| Siebel Installations > Install DB server configuration not working error SBL-GDB-00004, SBL-GDB-00010
Install DB server configuration not working error SBL-GDB-00004, SBL-GDB-00010
APPLIES TO:
Siebel System Software - Version: 7.5.3 SIA [16157] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3 [16157] Auto
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Sun Solaris 8
SYMPTOMS
SBL-GDB-00004, SBL-GDB-00010
The siebel DB srvr is residing on our app server on Win2000 sp2. When we click the configure DB server and try to 'Install DB' we are getting 'the table/index space you have entered does not exist in your database... Please ensure you enter the correct table/index space.
We have run the grantusr.sql without error. I verified that the SSE_Role is in the DB and the siebel and sadmin users have been created. We have created a table space named 'siebel' and created and index named 'index'. I have also verified that out ODBC connection (SiebSrvr_<Enterprise Server> has been installed and tested.
I'm not sure whether it is a connection issue or what. The tool doesn't tell me if I'm actually connectiong to see if those tables exist or not so I'm not sure where to look.
Is it possible to run a seperate shell script to configure the Siebel DB from a Windows Siebel DB server install similar to the Solaris installs?
CAUSE
Configuration/ Setup
SOLUTION
For the benefit of other readers, the Service Request was resolved after extending the table space, installation of the Siebel Application took place without error.
The main error encountered in the ddl_ctl.log file was:
"Running SQL statements against the database...
Merging table EIM_ACC_SRC_DTL 0s
Creating index EIM_ACC_SRC_DTL_U1 ...
HY000: [DataDirect][ODBC Oracle driver][Oracle]ORA-02216: tablespace name expected
Dropping index with the same column signature and retrying...
create unique index EIM_ACC_SRC_DTL_U1 on EIM_ACC_SRC_DTL
(IF_ROW_BATCH_NUM, ROW_ID)
tablespace INDEX
;
writeExecDDL error (pOperCallback UTLDbDdlOperIndCreate).
Error in MainFunction (UTLDbDdlDbMerge).
Error in Main function..."
We had also investigated that the codepage should have been on AL32UTF8 for UNICODE, but had been originally set up on WE8ISO8859P1.
| 
