CMS Sybase DB error using cmsdbsetup.sh on XIR2 Solaris

system · November 17, 2006, 10:21am

Hello,

I’m working on BO XI R2 - Solaris and I try to set up the CMS database (using cmsdbsetup.sh) on Solaris with a Sybase DB server.

cmsdbsetup.sh ask for this information:

Please specify Source CMS database connection information.
Please enter the service name for connecting to your Sybase database.
Please enter the user name for connecting to your Sybase database.
Please enter the user password for connecting to your Sybase database.

After set up this, I get the following errors:

err: Error: Failed to initialize current data source.
err: Error description: Unable to connect to the database using the provided connection string. Reason: Database Access Failure.
CMS Data Source setup finished.

I check with my Sybase DBA and it seems some information are missed during cmsdbsetup.sh: database server name (or ip), port…

I already work on Oracle and the description of the server name (or ip), port… was defined in tnsnames.ora

My Sybase DBA says there is a similar file that sould be set up:

at Sybase client level (interfaces file)
OR
at BusinessObjects level (odbc.ini or somewhere else)

Do you have any ideas, please ?
Do you know where cmsdbsetup.sh store given information during set up ?

Regards,
NoNoDiabolo.

nonodiabolo (BOB member since 2006-09-12)

system · November 20, 2006, 1:19pm

Hi,

In first cmsdbsetup store information into cms start file, but it initialize the cms data base so if you only modify the store information it can’t work.

The right way is to configure your sybase interface file (see your DBA).
U need to test connexion to sybase in console mode with isql run by the BOXI user (OS User)

Your errors can be produced by a problem with 32 bit sybase libs. BOXI is 32bit and need thepath to 32bits db client libraries

Regards

Thomas T. (BOB member since 2006-10-10)

system · November 21, 2006, 3:24pm

Hi Thomas T.,

Using isql, I can connect to appropriate CMS database without any problem with same information provided to cmsdbsetup.sh. So my Sybase “interface” file is correct.

On my last post, I used the “database name” information when cmsdbsetup ask for “service name” and I just get DB Access Error messages. Now I use the “server name”, and I get same errors and worst: an additional error, a “Segmentation Fault” !

But now, CMS tables are created (I can see them with isql tool).

The problem seems to be the way BO setup use the DB Client or the way the “connection string” send by BO to DB Client is done.
When browsing to settings files, I discovered something very special:
(from file data/.bobje…/.cms/.registry)

"AuditingDatabaseConnectString"="00@8000013CA66YdAeJjNebTDm?b]Ea`OVFH:X]\N^_j;lWobMn4PLHE1aM6IMkJC:ZM0Q;DjAdhU_DPeH0>SF[jaHWHQPjQWCKd"
"AuditingDatabaseDriver"="sybaseauditdbss"
"ConnectionTimeout"="600000"
"DatabaseConnectString"="00@8000013hEd:62_LROoBKX14<ZElHEJZ<M6PE>DHUS<VcGjb5MBbTSn9lD^enQ=MfjT9H=B]_k\=@XHR\leGj4D3Wjl3jY2neZ"
"DatabaseDriver"="sybasedatabasesubsystem"
"ServerState_TimeoutForPing"="10"
"ThreadTimeoutAfterNMinutes"="9"

DatabaseConnectString and AuditingDatabaseConnectString seem to be encrypted: is it “normal” ? Is there a way to specify host, port, db name, user and password with clear text here and what syntax should be used ?

It is maybe, as you suggested a 32 bit library problem: do you know if there is any workaround ? My Sybase client does not mention 32 or 64 bits information (OCS root sybase folder is: /opt/sybase/OCS-12_5/ )

Here is a sample of my .profile file:

export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8
export SYBASE=/opt/sybase
export SYBASE_OCS=OCS-12_5
export PATH=$PATH:$SYBASE/$SYBASE_OCS/bin:$SYBASE/$SYBASE_OCS/lib
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+${LD_LIBRARY_PATH}:}$SYBASE/$SYBASE_OCS/lib:/usr/openwin/lib/:/global/auriga/EnterpriseXIR2/boxir2/bobje/enterprise115/solaris_sparc

For information:

BusinessObjects XI Server R2 runs on Sun Solaris 5.8
DB Client is Sybase Open Client (OCS-12_5) v12.5.4
DB Server is Sybase Server v12.5.4
Settings & Logs files attached

Thanks for your help.

Best Regards,
NoNoDiabolo.
Settings & Logs.zip (200.0 KB)

nonodiabolo (BOB member since 2006-09-12)

system · November 21, 2006, 3:58pm

Hi,

I think your problem is realy due to using 64 bits libs. I’m not an Sybase expert, but with Oracle there where 2 different lib folder 1 for 64Bit and 1 for 32Bit. Ask to your DBA.

BOXI use some think like the windows registry table. it contain some configuration. Data base connexion string is store encrypted for security raisons. To change data base connexion string you need to use cmsdbsetup.sh.

Follow the 32/64Bits way, I think it’s the origin of your problem.

Regards[/quote]

Thomas T. (BOB member since 2006-10-10)

system · November 21, 2006, 4:21pm

Hi,

We have experianced problems on Solaris with the ORA Client 10.
The solution was to install an ORA Client 9.2.

Maybe it will help

Best regards,

bogdan agape (BOB member since 2004-09-08)

system · November 21, 2006, 5:42pm

My DBA confirms I use 32 bits libraries.

But I have news about my troubles…
[list]1) When I start from scratch (no tables in CMS database), cmsdbsetup.sh does not gives any errors
2) When I run another time (after first step) cmsdbsetup.sh, I get the “Segmentation Fault” Error.
3) Whatever the number of times and options I use when I run cmsdbsetup.sh (after step 2), I always get “Segmentation Fault” errors.
4) The only way to not get “Segmentation Fault” is to drop another time all CMS tables and to redefine DB settings (step 1).[/list]
I think cmsdbsetup.sh can connect to Sybase server, create tables but cannot retrieve some data and I really don’t know why…

My kind DBA has created a new Sybase Database (with UTF8 and 8KB block size as recommended on some forum topics) but we already get exactly the same issues (steps 1, 2 and 3).

I have no more idea :? (the best solution would be to trace messages between cmsdbsetup.sh and sybase client and between sybase client and sybase server)!

Thanks for your precious help.

Best Regards,
NoNoDiabolo,
BI Senior Consultant,
Old-BO-Guy.

nonodiabolo (BOB member since 2006-09-12)

system · November 21, 2006, 6:06pm

Does your unix user LANG and LOCALE are UTF8?
Have had a probleme with this, use UTF8 in upper case instead of in lower (sybase client doesn’t match with lower case)

Maybe it help You

Thomas T. (BOB member since 2006-10-10)

system · November 21, 2006, 6:27pm

Hi Thomas,

Yes My LANG & LOCALE are already set up (you can see my .profile on a previous post with attached file “Settings & Logs.zip”).

Extract of my .profile file:

export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8
export SYBASE=/opt/sybase
export SYBASE_OCS=OCS-12_5
export PATH=$PATH:$SYBASE/$SYBASE_OCS/bin:$SYBASE/$SYBASE_OCS/lib
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+${LD_LIBRARY_PATH}:}$SYBASE/$SYBASE_OCS/lib:/usr/openwin/lib/:/global/auriga/EnterpriseXIR2/boxir2/bobje/enterprise115/solaris_sparc

Thanks,
N N Diabolo.

nonodiabolo (BOB member since 2006-09-12)

system · November 22, 2006, 7:18am

Hi,

Sorry have pay attention to your bash profile .

In my bashrc file I haven’t sybase variables. I’ve only

source /pat/to/sybase/home/SYBASE.env

An other thing which can help your. I’ve never set BOE lib path to any LD_LIBRARY_PATH of the dozens installation/configuration I’ve done.

Last thing, the begin of your LD_LIBRARY_PATH, surprise me. Why

With { and ; intercalated ie (}:})? Why + ?

Regards

Thomas T. (BOB member since 2006-10-10)

system · November 22, 2006, 1:49pm

Hi Thomas,

My unix user does not have access to /opt/sybase/SYBASE.env file… But as recommended on BO XI R2 admin guide, I defined $SYBASE and $SYBASE_OCS variables properly. I think this part is well configured (because CMS tables are partially created through cmsdbsetup.sh).

The LD_LIBRARY_PATH syntax is a way to get a clean LD_LIBRARY_PATH (in case there is no value to avoid entry LD_PATH like “:/opt/sybase”…).
I try without this workaround, but no changes…

My issue may come from the right the user is granted to (from BO Support, db user should not be granted to “dbo” role)… I will check this with my DBA and come back to the forum (hope it’s THE solution ).

Regards,
N N Diab l

nonodiabolo (BOB member since 2006-09-12)

system · November 23, 2006, 6:36pm

[SOLUTION - WORKAROUND]

Good evening,

What a good day today…

The workaround given by BO-Support simply works!
I do not get errors or "Segmentation Fault any more

To summarize, BO XI R2 Install Unix Guide is missing something about CMS DB set up on Sybase.

The Sybase user does not have to be granted to “dbo” role. Only standard rights (create tables, drop tables, select into,…) must be defined for this user. Otherwise you will get “Segmentation Fault” and other errors.

My Sybase client and server version is v12.5.4 (for BO support it is v12.5.2).

Hope this help…

My 2 €,
N N Diabolo.

nonodiabolo (BOB member since 2006-09-12)

system · November 24, 2006, 6:02am

Good Job,

Did open a case on BO support ?

Regards

Thomas T. (BOB member since 2006-10-10)

system · November 24, 2006, 4:22pm

Hi,

Yes, I created a case that will be closed soon (but after creation of a “documentation enhancement request” by BO Support).

Regards,
N NoDiabolo.

nonodiabolo (BOB member since 2006-09-12)