Database error: 523 80

[Former Member]

Hi All,

I restarted our BusinessObjects BI 4.0 SP5 server on Linux and now, when I try to refresh my reports in BI Launch Pad, I get a "Database error: 523 80".

Can anyone help?

Thanks in advance and best regards,

Ron

[Former Member · Accepted solution]

Hi All,

I forgot to mention that we also have Data Services installed which has DataDirect drivers bundled.

On my ODBC.ini file, I used the DataDirect drivers from Data Services to use for BI LaunchPad.  We did an 'ls -l' command on the drivers and noticed that the modify date of the driver files are exactly one year ago.

Just a hunch, though, but could the drivers be expired for other uses other than for Data Services?

Thanks and best regards,

Ron

[Former Member · Accepted solution]

I will suggest to use the CS check tool to check the connection..

You can find more info on CS check on Dataaccess pdf page 44 onwards..

http://help.sap.com/businessobject/product_guides/sbo41/en/sbo41_data_acs_en.pdf

Also there is one thread discussing issue with CS check tool in Linux with nice info which you might want to check here

http://scn.sap.com/thread/1323387

[former_member188911 · Accepted solution]

Hi Ron,

if the problem started showing up after a reboot, it is likely that you exported and environment variable that should have been sourced in the profile.

Otherwise there may have been a change in configuration that would require reviewing step by step the db drivers setup

Thanks

Simone

[Former Member · Accepted solution]

Hi Simone,

But I did not reboot the server or the machine itself.  Only the BOBJ application using ./stopservers and ./startservers commands.

I'll check the environment variables.

Thanks and best regards,

Ron

[abhinav_shrivastava1 · Accepted solution]

Hi Ron,

First I would recommend to try re-sourcing the LD_LIBRARY_PATH.

If that doesn't help, try verfiying are you able to shoot SQL to DB server or not.

What is the Universe Type?

If its UNX, DSL-APS will come into picture so you can try creating a DSL-APS and test the behavior.

-Abhi

[Former Member · Accepted solution]

Hi Simone,

Thank you.  Echoing LD_LIBRARY_PATH shows up empty.

After re-sourcing the bash_profile, all is ok now.

Best regards,

Ron

[Former Member]

If your DB is Netezza you might want to check the KBA below

1794110 - Database error: 523 80. (IES 10901) when creating/refreshing Webi reports that use Netezza...

Suggest you to follow the same path for greenplum as mentioned for netizza and see if this makes any difference.... The driver details for greenpum can be viewed in this document http://help.sap.com/businessobject/product_guides/sbo41/en/sbo41_data_acs_en.pdf

Resolution

Please ensure the below requirements are met on the Processing Servers

1. Ensure you have installed the correct (64-bit) ODBC drivers for Netezza database
2. Edit your profile to include the following items
   1. LD_LIBRARY_PATH  - Ensure this path includes the 64-bit library path.  e.g. /App/nz/lib64
   2. PATH  - Ensure this path includes the path the 64-bit binaries for your database.  e.g. /App/nz/bin64
   3. ODBCINI  - This should point to the odbc.ini file that has your datasources defined
3. Update your odbc.ini file to make sure it has the following
   1. Updated driver path to point to the 64-bit drivers
   2. Has all of the DSN entries needed to run your reports
4. Check permissions on all of the drivers.  Each driver used will need execute permissions for the user that BI 4.0 is running as.
5. Test your connection outside of BI 4.0 using utils like nzodbcsql.  This will tell you if the driver is configured correctly.  Run this as the same user running the SIA in your system.

Tips on troubleshooting this issue:

• Restart the SIA after each change.  A lot of these things won't take affect until after a restart.
• Log off your terminal session and back in to load environment variables you have set in the profile
• Use the ldd <filename> command to check and see what "bit" a file is if you aren't sure.   It will show 64bit or 32bit in the output.
• Use strace or truss to do a system level trace on the WIReportServer process to get deep dive tracing if you really aren't sure where this is breaking

[Former Member]

Hi Durgamadhab,

The resolution requires changing Linux system files (which we haven't touched) when what we did was just a restart of the BOBJ server and not the machine itself.  Before restarting, our reports were working fine.

Thanks and best regards,

Ron

[Former Member]

Looks like the rather unhelpful contact your administrator message.

What type of database are you trying to connect to?

[Former Member]

Hi Mark,

I am using Greenplum.  We use ODBC3 as connection type when creating the Universe as it works unlike using the Greenplum 4 connection type.

I found this in the logs:

<ERROR COMPONENT="WIS" ERRORCODE="10901" ERRORTYPE="USER" MESSAGE="Database error: 523 80. (IES 10901)" PREFIX="ERR">
< DEBUGINFO BORESULT="5" FILENAME="kc3cdbtbdacs.cpp" LINEPOSITION="2105" MODULENAME="C3_CS"/>
<REQUESTINFO COMMANDID="0" COMMANDNAME="Refresh batch" DPID="DP0" DPLONGNAME="Query 1 - Test_Universe" DPNAME="Query 1"/>
< REASON>
<CONTENT>
</CONTENT>
</REASON>
</ERROR>
</ERRORS>

Best regards,

Ron