Siebel Tools >  Siebel Tools with Oracle XE errors Part 1

Siebel Tools with Oracle XE errors Part 1

An internal error has occured within the authentication subsystem for the Siebel Application . Please Contact your system administrator for assistance (SBL-DAT-00565)

Siebel CRM - Version 15.4 [IP2015] and later

User is unable to login to Siebel tools with Oracle XE database .  The following error was thrown ..

An internal error has occured within the authentication subsystem for the Siebel Application . Please Contact your system administrator for assistance (SBL-DAT-00565)

Incorrect oracle client path and  connect string information in tools.cfg 
 
The Oracle client path provided during installation : E:\Siebel\15\Tools\network\admin and connect string = XE. 

From oraInstall2015-12-01_06-08-21-AM.out,

s_XE_Install_Bat_RegOutputFile = C:\Users\BRIANP~1.BUR\AppData\Local\Temp\regoutput.txt*****

TNS Path (E:\Siebel\15\Tools\network\admin) does not exist. Creating it

-1. In the [DataSource] section, add the following line in tools.cfg

LOCAL_XE = LOCAL_XE

-2. Add a  ConnectString = LOCAL_XE under [LOCAL_XE] in tools.cfg

-3.  Manually added tns entries for LOCAL_XE  under $Oracle_Client/network/admin

-4.  Run  local database setup script, using a command similar to the following ..

This command reads custom schema and data from the enterprise database and applies it to the existing local database that was created when you installed Oracle Database XE with Siebel Tools.

SIEBEL_TOOLS_ROOT\bin\LocalDbSetup.exe -s $SiebelTools -o "$ODBCDataSource" -t $TableOwner -u $username -p $password -r "Siebel Repository" -d $ODBCDataSource_XE -x "$OracleXEInstallationPath" -l $logfilename -w $debugmode -y "Runtime Tables"

Refer Siebel Bookshelf : http://docs.oracle.com/cd/E63029_01/books/ConfigApps/RoadMap10.html#wp1095734 for details

Eg: 

C:\Siebel\15\Tools\bin\LocalDbSetup.exe -s C:\Siebel\15\Tools -o ENT_DSN -t SIEBEL -u SADMIN -p SADMIN -r "Siebel Repository" -d LOCAL_XE -x C:\Siebel\15\Tools\oraclexe -l C:\oraclexe.txt -w y -y y

Local XE Database Extract Error ORA-28001

On : 15.10 [IP2015] version, Installation

When attempting to extract a Local Siebel Tools database, the following error occurs.

ERROR
-----------------------
ODBCSQL: (ODBC SQL Interface) Start at 5/17/17 16:00 (pid 8240)
Spooling started to "C:/Siebel/15/Tools/BIN\LocalDbTemplate\tablelist.out".
ODBC error S1000 in SQLConnect:
[tp][ODBC Oracle driver][Oracle]ORA-28001: the password has expired
(native error 28001).
Unable to login using specified ODBC parameters.

ODBCSQL: Exit at 5/17/17 16:00 (status -1)

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Run C:\Siebel\15\Tools\bin\LocalDBSetup.exe -s C:\Siebel\15\tools -o "CRM_15_DEV" -t SIEBEL -u MRJ7 -p ******** -r "Siebel Repository" -d LOCAL_XE -x "C:\Siebel\15\tools\oraclexe" -l C:\Siebel\15\Tools\Bin\LocalDBSetup.log -w N -y "Runtime Tables"
2. Error occurs at stage 4 of 7 (Truncate the existing data of LOCAL_XE)
3. [tp][ODBC Oracle driver][Oracle]ORA-28001: the password has expired

The issue is caused by the following setup: The SIEBEL user is expired in the SERVER database.
 
EVIDENCE OF CAUSE
---------------
[tp][ODBC Oracle driver][Oracle]ORA-28001: the password has expired

SUPPORT OF CONCLUSION
---------------

USERNAME ACCOUNT_STATUS
------------------------------ --------------------------------
SIEBEL EXPIRED
 

To implement the solution, please execute the following steps:

1. Become database admin
First log into your host running oracle and become the oracle user by typing the following into the command window:
sqlplus /nolog
SQL> connect / as SYSDBA
Connected
SQL>

2. List the Expired accounts
select username, account_status from dba_users where ACCOUNT_STATUS LIKE '%EXPIRED%';
USERNAME ACCOUNT_STATUS
------------------------------ --------------------------------
ORACLE_OCM EXPIRED & LOCKED
XDB EXPIRED & LOCKED
SIEBEL EXPIRED
HR EXPIRED & LOCKED
DBSNMP EXPIRED & LOCKED
DIP EXPIRED & LOCKED
OUTLN EXPIRED & LOCKED
CTXSYS EXPIRED & LOCKED
MDSYS EXPIRED & LOCKED
XS$NULL EXPIRED & LOCKED
APPQOSSYS EXPIRED & LOCKED
11 rows selected.

3. Activate an expired account
Assign a password to reactivate the account:
ALTER USER SIEBEL IDENTIFIED BY password;

Full Get on Siebel LOCAL XE database results in ORA-30036: unable to extend segment 

ERROR:

ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS1'

 
STEPS:

DB-Extract created and successfully initialized on client computer
2. Do a full get -> successfully
3. Do another full get the next day -> not successfully -> error message:
S1000 (30036): [tp][ODBC Oracle driver][Oracle]ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS1'

Siebel Tools - Version 16.5 [IP2016] and later
Information in this document applies to any platform.

ISSUE:

Full Get on Siebel LOCAL XE database results in ORA-30036: unable to extend segment 

ERROR:

ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS1'
 
STEPS:

1. DB-Extract created and successfully initialized on client computer
2. Do a full get -> successfully
3. Do another full get the next day -> not successfully -> error message:

S1000 (30036): [tp][ODBC Oracle driver][Oracle]ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS1'
 
This issue is caused by a product defect.

A workaround has been provided by the Engineering Team: use database extract component parameter "ExtractRepos" so that the mobile client is extracted with the repository tables like S_INT_FIELD, and increase Undo tablespace size.

For more info on this check: Siebel Remote and Replication Manager Administration Guide > Reference Materials for Siebel Remote > Server Component Parameters > Parameters of the Database Extract Server Component

     "ExtractRepos" - Configures Siebel Remote to include repository tables in a database extract. Values are TRUE and FALSE.

                             If the Extract all Repository Tables parameter is set to TRUE, then the Get is not necessary. Not using the Get can reduce the amount of time that you require to configure an environment for a developer.

In IP2017 local XE feature is not supported.