SQL1762N Unable to connect to database because there is not enough space..

[Former Member]

During the testing of an ODBC connection wich I created in a SAP BODS installation, created via the 'odbcad32'

I get the following error

SQL1762N Unable to connect to database because there is not enough space to allocate active log files. SQLSTATE=08004

Strange thing is that I also get this now on the other databases for BODS which are already installed.

I have also tried it via sap business objects xi 3.2 --> business object data services --> Data services repository manager

but than it comes with a message being.

Cannot open connection to the repository. The error message from the underlying DBMS is <ODBC call <SQLDriverConnect> for data source <dsp_prof> failed: <[IBM][CLI Driver] SQL1531N The database alias "DSP_PROF" could not be found in the db2dsdriver.cfg configuration file.

>. Notify Customer Support.>. (BODI-20006)

But when I try it at a collegeages computer, it comes also with the same error I get via the odbcad32 being the

SQL1762N Unable to connect to database because there is not enough space to allocate active log files. SQLSTATE=08004

My log directory is 4gb and only used for 1 %

Any ideas to get this running?

[Former Member · Accepted solution]

Hello,

Problem seems to be related to the number of log files (Primary/Secondary logs). Normally we keep less number of primary log files and more number of seconday logs.

Did you increase the number of primary or secondary logs recently ? Try to reduce the parameter and then test the connection.

http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=%2Fcom.ibm.db2.luw.messages.sql...

http://database.ittoolbox.com/groups/technical-functional/db2-l/db2-aix-message-sql1762n-2547634

http://database.ittoolbox.com/groups/technical-functional/db2-l/how-many-logfilsiz-1254448

http://dbaspot.com/db2-udb/247122-transaction-log-setting-prevent-connection.html

Thanks

[Former Member · Accepted solution]

thnx problem is solved by adjusting the parameter and on increasing the logsiz.

[teddylv_andersen2]

In a new installation of SAP NetWeaver 7.5, this happened to me because fo the fact that the filesystem was created with the <DBSID> in lower case letters.