Internal Exception: java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection 

SYMPTOMS

Internal Exception: java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection

Error Code: 17002

CAUSE

 Changed the database host address and the configuration files still  has the old database address not able to contact the database

 

SOLUTION

To implement the solution, please execute the following steps:

1. Updated the corrects database host names in the config files and restart the server. so that server will connect to the database

a) config.xml ( user_projects/<your_domain>/config)

b)jps-config.xml ( user_projects/<your_domain>/config/fmwconfig)

c) jps-config-jse.xml ( user_projects/<your_domain>/config/fmwconfig)

d)jdbc folder ( user_projects/<your_domain>/config/)

save the files and restart the server

Oracle on Solaris Fixing the ORA-27102 out of memory Error

ORA-27102: out of memory Error while starting the database

Symptom:

As part of a database tuning effort you increase the SGA/PGA sizes; and Oracle greets with an

ORA-27102: out of memory

error message. The system had enough free memory to serve the needs of Oracle.

SQL> startup

ORA-27102: out of memory

SVR4 Error: 22: Invalid argument

Diagnosis

$ oerr ORA 27102

27102, 00000, "out of memory"

// \*Cause: Out of memory

// \*Action: Consult the trace file for details

% prtconf | grep Mem

Memory size: 32760 Megabytes

% id -p

uid=59008(oracle) gid=10001(dba) projid=3(default)

% prctl -n project.max-shm-memory -i project 3

project: 3: default

NAME    PRIVILEGE       VALUE    FLAG   ACTION                       RECIPIENT

project.max-shm-memory

        privileged      7.84GB      -   deny                                 -

        system          16.0EB    max   deny                                 -

% prctl -n project.max-shm-memory -r -v 10G -i project 3

% prctl -n project.max-shm-memory -i project 3

project: 3: default

NAME    PRIVILEGE       VALUE    FLAG   ACTION                       RECIPIENT

project.max-shm-memory

        privileged      10.0GB      -   deny                                 -

        system          16.0EB    max   deny                                 -

How to Enable and Disable Firewall in Solaris server

To Enable the Firewall:

svcadm enable svc:/network/ipfilter:default

To Disable the Firewall:

svcadm disable svc:/network/ipfilter:default

To check the status of the Firewall:

ipfstat -io

Siebel Server is not starting because of the error "Unable To Initialize The Database Environment -- Unable To Start Common Api"

Unable To Initialize The Database Environment -- Unable To Start Common Api

SYMPTOMS:

Server seems not to be connecting to the database successfully,

Srbroker.log file shows the following messages:

GenericLog GenericError 1 0 2011-08-02 13:26:26 (srbthrd.cpp (3920) err=3200016 sys=0) SBL-SRM-00016: Unable to initialize the Database environment -- Unable to start common api 

GenericLog GenericError 1 0 2011-08-02 13:26:26 (srbmtsrv.cpp (71) err=3200016 sys=0) SBL-SRM-00016: Unable to initialize the Database environment -- Unable to start common api 

SrbLayerLog Error 1 0 2011-08-02 13:26:26 Main Init fails 

GenericLog GenericError 1 0 2011-08-02 13:26:26 (smimtsrv.cpp (1061) err=3200016 sys=0) SBL-SRM-00016: Unable to initialize the Database environment -- Unable to start common api

CAUSE:

The following file was missing in the installed folder.

'C:\Siebel78\siebsrvr\sqltempl\comdb42.sql'.

SOLUTION:

The odbc connection was tested and the server was able to connect to Siebel database.

Since customer backs up the environment regularly, the file comdb42.sql was restored from the backup copy to the appropriate folder 'C:\Siebel78\siebsrvr\sqltempl'.

Srbroker error solved and the Server started up successfully.

Siebel does not start because System component initialization timed out

SBL-SMI-00151: System component initialization timed out. System will shut down

Error in the Log File   :

ServerLog ProcessExit 1 000fd13855f816e4:0 2015-09-16 12:52:45 SRBroker 3188 TERMINATED Process 3188 was terminated

NotifyEvt NotifyErrors 1 000fd13855f816e4:0 2015-09-16 12:52:45 SBL-ADM-09152Could not send a notification message because we could not connect to the notification pipe (ENTSRVPRD_SRVTI339_7), retCode = (9609), nSysErr = (0)

GenericLog GenericError 1 000034de55f911c8:0 2015-09-16 12:57:39 (schedule.cpp (2296) err=1376409 sys=6) SBL-SMI-00153: SRBroker NOT READY Component is not ready.

GenericLog GenericError 1 000034de55f911c8:0 2015-09-16 12:57:39 (schedule.cpp (2237) err=1376408 sys=0) SBL-SMI-00152: TIMEOUT Component initialization for priority level 2 timed out after 300 s.

GenericLog GenericFatal 0 000034de55f911c8:0 2015-09-16 12:57:39 (schedule.cpp (2248) err=1376407 sys=0) SBL-SMI-00151: System component initialization timed out. System will shut down.

GenericLog GenericError 1 000034de55f911c8:0 2015-09-16 12:57:39 (schedule.cpp (708) err=1376407 sys=0) SBL-SMI-00151: System component initialization timed out. System will shut down.

GenericLog GenericError 1 000034de55f911c8:0 2015-09-16 12:57:39 (schedule.cpp (146) err=1376407 sys=0) SBL-SMI-00151: System component initialization timed out. System will shut down.

ServerLog ProcessExit 1 000fd13855f816e4:0 2015-09-16 12:57:39 SCBroker 4304 TERMINATED Process 4304 was terminated

GenericLog GenericError 1 000fd12d55f816e4:0 2015-09-16 12:57:39 (listener.cpp (434) err=1376297 sys=126) SBL-SMI-00041: Internal: Could not start the scheduler thread (1376407)

GenericLog GenericError 1 000fd12d55f816e4:0 2015-09-16 12:57:39 (lstnsvc.cpp (181) err=1376297 sys=0) SBL-SMI-00041: Internal: Could not start the scheduler thread (1376407)

ServerLog ServerShutdown 1 000fd12d55f816e4:0 2015-09-16 12:57:39 Scheduler error

SCBroker logs shows below errors     :

2021 2015-09-16 12:52:39 0000-00-00 00:00:00 -0300 00000000 001 ffff 0001 09 SCBroker 3145731 4304 3044 D:\Siebel\8.1.1.11.0\ses\siebsrvr\log\SCBroker_0003_3145731.log 8.1.1.11 SIA [23030] ENU

GenericLog GenericError 1 0000000255f910d0:0 2015-09-16 12:52:39 (scbcomp.cpp (447) err=4653071 sys=0) SBL-SCB-00015: The component is down or not available on this server.

GenericLog GenericError 1 0000000255f910d0:0 2015-09-16 12:52:39 (scbcomp.cpp (266) err=4653071 sys=0) SBL-SCB-00015: The component is down or not available on this server.

Upon Siebel server startup, the SRBroker component does not initialize and the SCBroker logs for similar timestamp shows that the component is down. The system components were not initializing and timing out and this could be the reason why the Siebel server was not starting up.

CAUSE    :  

The cause of the issue was determined to be with the Siebel server missing the SQLTEMPL folder. This was identified after comparing the working and non-working servers and it was identified that the SQLTEMPL folder was missing on the problematic server.

The Siebel installation procedure populates this SQLTEMPL folder with SQL files, containing SQL templates that can be used to create SQL statements that the Siebel Server uses to perform for specific database operations. This was missing and hence the components could not initialize as none of the pre-defined queries could be executed because of the missing directory.

SOLUTION:

The solution action plan for the issue is as below:

1. Stop the Siebel and gateway server.

2. Copy the SQLTEMPL folder from the working server to the non-working server

3. Restart the Siebel gateway and Siebel server and check to see if the system component initializes and does not timeout and bring down the Siebel server.

After copying the SQLTEMPL folder from working server, the Siebel server started up without any issues.

How to change the Siebel DB user Password

Changing the Table Owner (DBO) Password

The Siebel Database Server installation script also creates a database Table Owner (DBO) account used to modify the Siebel database tables. The default user ID and password for this database account are SIEBEL and SIEBEL (case-sensitive). You should change the password for this account.

The Table Owner is used to reference table names in SQL statements that are generated by the Siebel application (for example, SELECT * FROM SIEBEL.S_APP_VER).

A corresponding parameter is configured for the Siebel Enterprise, named Table Owner (alias TableOwner). Siebel application modules such as Application Object Managers (AOMs) use this parameter value to provide the Table Owner name when generating SQL for database operations. You specify the Table Owner name during Siebel Enterprise Server configuration, which provides a value for this parameter.

A related parameter is Table Owner Password (alias TableOwnPass). For most database operations performed for Siebel Business Applications, the Table Owner password does not need to be provided. For this reason, this parameter is not configured during Siebel Enterprise Server configuration.

However, if the Table Owner Password parameter is not defined, then the Table Owner password may sometimes need to be provided manually.

Note the following requirements for changing the Table Owner password:

If you have not defined the Table Owner Password parameter, then the Table Owner password only has to be changed in the Siebel Database. (The changed password may also need to be provided manually for certain operations.)

If you have defined the Table Owner Password parameter, then you must also update the value for this parameter when you change the password in the Siebel Database.

To change the password for the Table Owner account

Change the Table Owner password for the Enterprise, using Server Manager.

Log into a Siebel employee application, such as Siebel Call Center.

From the application-level menu, choose Navigate > Site Map > Administration - Server Configuration > Enterprises.

Click the Parameters tab.

In the Enterprise Parameters list, locate the Table Owner Password parameter (alias TableOwnPass).

In the Value field, type in the new value, then commit the record.

If you have Siebel Developer Web Client users, also change the value for the TableOwnPass parameter in the [ServerDataSrc] section of each application configuration file, such as uagent.cfg for Siebel Call Center. This step must be done for each user's Siebel client installation.

Change the password in the database.

alter user siebel identified by ******;

Restart the Siebel Server.