cancel
Showing results for 
Search instead for 
Did you mean: 

Content Server- SQLConnect failed - Invalid Command State

2,487

Dear experts

Recently I have installed a SAP Content Server (7.53) with MaxDB 7.9 on SLES 15 SP1

When creating access the server info file, I get the following error:

contRepStatus="offline";contRepStatusDescription="SQLConnect failed (DBPARAMETERS): [SAP AG][LIBSDBOD SO][SAP MaxDB] General error;-10210 Invalid command state (No prepared SQL command), ec=-10210, rc=-1

This is my cs.info file:

Also when checking OAC0 I am able to connect to the repositories, but they are showing as offline.

I am able to connect to the database in MaxDB studio and use SQL editor, so it's not an issue with accessing the database I think.

Help is appreciated.

Thanks in advance!

Kr,
Brent

Accepted Solutions (0)

Answers (3)

Answers (3)

kathleen_a_sales
Explorer

My issues are now fixed, thank you so much for this post.

beernab
Explorer
0 Kudos

No problem, glad I could help.

0 Kudos

Hi Kathleen Sales,

I had similar issues after installed a SAP Content Server (7.53) with MaxDB 7.9 on SLES 12.sp5, while accessing content server in browser getting errors like ontRepStatusDescription="SQLConnect failed (DBPARAMETERS): [SAP AG][LIBSDBOD SO][SAP MaxDB] General error;-10210 Invalid command state (No prepared SQL command), ec=-10210, rc=-1";

Any support on prioirty is highly appriciated , thank you

Sarikar

kathleen_a_sales
Explorer

Hi brent Im having the same issue can you please elaborate how you did this?

"This issue has been resolved by adjusting the existing UID & GID of several DB owner accounts, which were unable to execute some SQL scripts."

kathleen_a_sales
Explorer
0 Kudos

how di you know whats the right UID and GID?

beernab
Explorer
0 Kudos

Hi Kathleen

Are you performing a clean install? For me this was a migration from an existing Content Server.
I've checked the old user & group id and made sure it was the same for the database software owner (sdb) & instance software owner (SIDsdb)

You can also set this for SIDadm user.

Please refer to https://www.thegeekdiary.com/how-to-correctly-change-the-uid-and-gid-of-a-user-group-in-linux/
Also check /etc/fstab if all UID entries are correct.

kathleen_a_sales
Explorer
0 Kudos

Will try this one, im also doing migration from an existing content server. Thanks for this!

kathleen_a_sales
Explorer
0 Kudos

Hi brent I would like to clarify that the sdb and sqdsdb UID and GID are the same? and they are patterned to the Old Content Server?

karan_moudgil
Discoverer
0 Kudos
Thanks Kathleen, I was facing the same issue and it was resolved by changing the UID of database software owner and instance software owner
sumitjais
Active Contributor
0 Kudos

Hi Brent,

Please try the below and let's see if it helps.

Add the below two entries alongwith others in cs.conf for each of the contRep.

AdminSecurity=0

PSEDir=<path to security directory>

Restart the apache.

Go to tcode OAC0 and exchange the certificate. Confirm the same in CSADMIN tcode.

beernab
Explorer
0 Kudos

Hi Sumit Jaiswal

Thanks for your reply.

As per SAP Content Server 7.5 some parameters are deprecated (https://launchpad.support.sap.com/#/notes/2786364)
PSEDir is obsolete as the repository certificates are now stored in the instance's security directory (SECUDIR).
AdminSecurity parameters are handled by the authentication handler in the profiles (icm/HTTP/auth_0).

I forgot to mention that this was a migration from a SAP Content Server 6.4. This issue has been resolved by adjusting the existing UID & GID of several DB owner accounts, which were unable to execute some SQL scripts.

Kind regards,
Brent

sumitjais
Active Contributor
0 Kudos

Thanks for the update Brent.

Glad to know that the issue got resolved.

kathleen_a_sales
Explorer
0 Kudos

Hi brent im having the same issues and we are doing the same thing how did you od this? can you please elaborate?

"This issue has been resolved by adjusting the existing UID & GID of several DB owner accounts, which were unable to execute some SQL scripts."