Siebel Administration >  Siebel Database Extract and errors

Siebel Database Extract and errors

After a new deployment or upgrade in Siebel, we should delete data from tables as shown below After a new deployment or upgrade in Siebel, we should delete data from tables as shown below 

truncate table  SIEBEL.S_DOCK_STATUS; 

truncate table  SIEBEL.S_DOCK_TXN_LOG;

truncate table  SIEBEL.S_DOCK_TXN_LOGT;

truncate table  SIEBEL.S_DOCK_TXN_SET;

truncate table  SIEBEL.S_DOCK_TXN_SETT;

Generate new Database with this command against Server Manager:

start task for comp gennewdb with DbaPwd=SQL

SQL is the default password. If your password has been changed, use the new password.

To run dbxtract for two users called SIEBELUSER1 and SIEBELUSER2, the command for server manager is

run task for comp DbXtract server SIEBEL_SERVER_NAME with Client="SIEBELUSER1,SIEBELUSER2",InitMethod="Sql Anywhere",EncryptLocalDbPwd="False",EncryptLocalDbMethod="None",Username="SADMIN",Password="SADMIN_PASSWORD"

The parameter names in Server manager and GUI are different. here are some of the values.

You can find them when you open the Parameter Applet in GUI from Administration -> Server Management -> Jobs

Full Name in GUI                         Server Manager  Param Name

16K Tablespace Name                          16KTblSpace

32K Tablespace Name                          32KTblSpace

Alert Level                                           AlertLevel

CD directory                                         CDDir

Client DBA Password                             ClientDBAPwd

Client Database encryption key              EncryptLocalDbKey

Client Database encryption method        EncryptLocalDbMethodClient

Name                                                  Client

Data File Type                                      DataFileType

DataBase Rollback Segment Name         DBRollbackSeg

Database Init Method                            InitMethod

Database template file name                  DbTmplFile

Debug Flags                                          DebugFlags

Debugger                                             dbg

Disable Autocommit                              DB2DisableAutoCommit

Do not send events to logging                BypassHandler

Enable client Db Txn log                         ClientDbTxnLog

Encrypt client Db password                    EncryptLocalDbPwd

End of Line character sequence              LogEol

Error Flags                                            ErrorFlags

Extract all Repository Tables                  ExtractRepos

Language Code                                     Lang

Log Print Timestamp                             LogTimestamp

Log directory                                        LogDir

Maximum Ping Time                              MaxPingTime

Move Siebel Remote client                      Move

ODBC Data Source                                Connect

Password                                              Password

SQL Dump File                                      SQLFile

SQL Trace Flags                                    SQLFlags

Siebel File System                                 FileSystem

Siebel Repository                                  Repository

Trace Flags                                           TraceFlags

Name                                                   Username

The log file should be in the logs folder and will start with name DbXtract. e.g. DbXtract_0039_40882467.log
Here are the error messages that I have encountered last week.

SBL-SMI-00077: Component error, see the trace file for more inf(smisched.cpp (923) err=1376333 sys=0) SBL-SMI-00077: Component error, see the trace file for more information

SBL-ADM-60070: Error reported on server 'NCVSAPPE301' follows:

SBL-SVR-01042: Internal: Communication protocol error while instantiating new task

SBL-SMI-00077: Component error, see the trace file for more information

SBL-SMI-00077: Component error, see the trace file for more information

GenericLog GenericError 1 000000085c170920:0 2018-12-17 11:13:33 Unable to find node for remote user or mobile user in database.

GenericLog GenericError 1 000000085c170920:0 2018-12-17 11:13:33

Message: GEN-13, Additional Message: Updated 0 rows

Solution: 

We need to extract the user with Parameter Move Siebel Client = True

In Servermanager the command would be

run task for comp DbXtract server SIEBEL_SERVER_NAME with Client="SIEBELUSER1,SIEBELUSER2",InitMethod="Sql Anywhere",EncryptLocalDbPwd="False",EncryptLocalDbMethod="None",Move=True,Username="SADMIN",Password="SADMIN_PASSWORD"

We faced similar error messages

GenericLog GenericError 1 0000029e539765b5:0 2014-06-10 17:40:13

Message: GEN-15,

Additional Message: UTL_NODE_MWC_TYPE_SEL

or 

GenericLog GenericError 1 0000029e539765b5:0 2014-06-10 17:40:13

Message: GEN-15,

Additional Message: UTL_LDEL_RBR_TXN_SEL

or 

GenericLog GenericError 1 0000029e539765b5:0 2014-06-10 17:40:13

Message: GEN-13,

Additional Message: UTL_LDEL_RBR_TXN_EX_FILE_SEL

These can be solved by either using the Move command or checking the versions

run this SQL as siebel (sometimes any siebel user)

SELECT DB_SCHEMA_VER, DB_MINOR_VER, DB_MAINT_VER, CUSTOM_SCHEMA_VER, CUSTOM_DOCK_VER FROM SIEBEL.S_APP_VER;

You should be able to see the versions of your system.

Ask in oracle support webif the versions are correct. I could not find any good documentation about this.

There are a few points that you should note that can help you debug.

We should check which version of SQLs the DBXtract is using.

8.1.1.11   till 8.2X should use comdb48.sql 

Versions 15.x should use comdb50.sql

comdb50.sql and comdb48.sql should be present in the Siebel Tools folder of the server.

If you have an older version , e.g. with Siebel 15.x you can find only comdb45.sql, then you have an installation error.