6.2.1 database creation fails - dynamically allocated hardware resources

Document ID : KB000050977
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Related Issue/Questions:

Issue- $NH_HOME/sys/ehUsers.cfg cannot be created during installation
Issue- Oracle halts in the middle of the createDb and returns the following errors;

Check the Oracle alert log to see if any trace files were written when the checkpoint process died.

ORACLE_HOME/admin/bdump/EHEALTH/

Error message:

Grant succeeded.
Grant succeeded.
PL/SQL procedure successfully completed.
GRANT aq_administrator_role TO system WITH ADMIN OPTION
*
ERROR at line 1:
ORA-00469: CKPT process terminated with error
ORA-07445: exception encountered: core dump [kgskhighthreshold()+72]
[SIGSEGV] [Address not mapped to object] [0x0000001F6] [] []

In alert log, look for something like this;

Detected change in CPU count to 25
Wed Aug 11 09:49:44 2010
Errors in file /opt/ehealth/ora-bin/10g/admin/bdump/xxxxxxx/xxxxxxx_ckpt_19055.trc:
ORA-07445: exception encountered: core dump [kgskhighthreshold()+72]
[SIGSEGV] [Address not mapped to object] [0x0000001F6] [] []

Make note the line where it says that CPU count changed to 25.

Causes of this problem:

You had forgotten to assign a fixed amount of CPU's for the zone. The OS dynamically allocates hardware resources.

The CPU count increases every time eHealth installation is run.

Problem Environment:
Solaris Zones.

Solution:

Fix:

This is not supported by Oracle.

Your hardware team will have to allocate static resources.

There are two possibilities for resource allocation (CPU).

You can assign a static amount of CPU (cores) to the System, which can be a SUN Solaris Zone or let the OS of the global Zone assign CPUs dynamically to the Zone.

If you chose the latter, the OS will assign additional CPUs when the load goes up for that Zone.

Normally, you will need to assign a fixed amount of CPUs to a Zone.

After assigning a fixed amount of CPUs installation will complete.