SQL access not possible (LC10 / LiveCahce)

[Former Member]

Hi All!

I have installed my SCM system and LiveCache Client on the iSeries. My LiveCache Server is installed on a Windows 64-bit Server. I am following the post steps to Initialize LiveCache:

To initialize the liveCache instance LCA:

a) Choose Back (F3). (in LC10)

The liveCache: Initial Screen re-appears.

b) Enter LCA in the Name of database connection field.

c) Choose liveCache: Monitoring.

In the tree structure select <LC_NAME>(<host name-LC_Name>) Administration and

double-click on Operating.

The liveCache Administration menu appears.

e) From the menu, choose Administration Initialize liveCache

Several dialog boxes appear.

f) Confirm with Yes.

But when the screen comes up after selecting LiveCache Monitoring, up in the left hand corner, there is an '!' that reads: SQL access not possible .

Has anyone encountered this problem?

Thanks!

Diana

[dorothea_stein]

Hi Diana,

usually that happens when some piece of software or configuration is missing. Check for example whether you have the MaxDB DBSL in the kernel directory (dbsdbslib.o). You also need sapdbmrfc. (Both are part of the new(!) LCC patch.) Also check for libperfstat.a.

In general, check the dev trace. It should give us a hint what's wrong.

Best regards,

Dorothea

[Former Member]

Hi!

The dbsdbslib.o and sapdbmrfc are in the kernel directory. The libperfstat.a is in the directory /sapdbas4/lib as instructed by note 1081634. Does it need to be in the kernel directory as well?

Here is my developer trace file: (implies a codepage problem, I found note 680556, which looks promising, but I am on SCM 5.0, and I selected UNICODE for my install)

B New connection 1 created

B Connect to LCA as SUPERDBA with sapliv01-LCX

C

C DBSDBSLIB : version 700.08, patch 0.104 (Make PL 0.107)

C MAXDB shared library (dbsdbslib) patchlevels (last 10)

C (0.104) Update statistic with empty schemas (note 1041547)

C (0.095) MaxDB DBSL patch collection 1 2007 (note 1014270)

C (0.082) MaxDB DBSL patch collection 3 2006 (note 991258)

C (0.079) MaxDB DBSL patch collection 2 2006 (note 984406)

C (0.068) MaxDB DBSL patch collection 1 2006 (note 962708)

C (0.051) DB50 perm block defect (note 934194)

C (0.046) ADBC: invalid data when fetching cursor with hold (note 925337)

C (0.045) Signal 11 during creation of BIA index (note 920743)

C (0.038) MaxDB DBSL patch collection 2 2005 (note 908602)

C (0.034) Livecache unicode connect (use SDK 7.6.0 b11) (note 901576)

C

C

C Loading SQLDBC client runtime ...

C SQLDBC SDK Version : SQLDBC.H 7.6.0 BUILD 002-121-083-965

C SQLDBC Library Version : libSQLDBC 7.6.3 BUILD 008-123-159-187

C SQLDBC client runtime is MaxDB 7.6.3.008 CL 159187

C SQLDBC supports new DECIMAL interface : 0

C SQLDBC supports VARIABLE INPUT data : 1

C Try to connect as SUPERDBA/<pwd>@sapliv01-LCX on connection 1 ...

C Attach to SAP DB : Kernel 7.6.00 Build 029-123-130-265

C Database release is SAP DB 7.6.00.029

C INFO : Database 'LCX' instance is running on 'sapliv01'

C INFO : LVC DEFAULTCODE = ASCII

C *** ERROR => different codepage: application=UNICODE, LVC=ASCII

[dbslsdb.cpp 4668]

B ***LOG BY2=> sql error -4025 performing CON [dbds#1 @ 1044] [dbds 1044 ]

Thanks,

Diana

[dorothea_stein]

Hi Diana,

that is indeed a codepage problem. liveCache believes that it contains ASCII data where there should be Unicode.

Logging on to liveCache via DBMGui, you can check whether extended parameter _UNICODE is set to "YES". That's a prereq (Unicode catalogs).

There is a second parameter DEFAULT_CODE, which indicates what column type will be created by default. According to the MaxDB folks I just talked to it should not matter what that parameter is set to: liveCache initialization should have created all tables with the right codepage.

They suggest that you open a customer message to them (BC-DB-LVC).

Best regards,

Dorothea

[Former Member]

Thank you! My message is open and they are looking into the issue.

-Diana

[Former Member]

Hi again. I logged into the SQL Studio, and the user SAP<SID> shows UNICODE, but the user DBSERVICE shows DEFAULT. This is not correct, is it?

Thanks,

Diana

[dorothea_stein]

Hi Diana,

not sure (I'm really not the expert here), but I believe I have read that user DBSERVICE has something to do with the MaxDB replication infrastructure (Synchronization Manager), so that I would not be sure how you can drive from that comparison...

Best regards,

Dorothea

[former_member229109]

Hello Diana,

As I saw in your posts::

"

B Connect to LCA as SUPERDBA with sapliv01-LCX

...

Try to connect as SUPERDBA/<pwd>@sapliv01-LCX on connection 1 ...

C Attach to SAP DB : Kernel 7.6.00 Build 029-123-130-265

C Database release is SAP DB 7.6.00.029

C INFO : Database 'LCX' instance is running on 'sapliv01'

C INFO : LVC DEFAULTCODE = ASCII

C *** ERROR => different codepage: application=UNICODE, LVC=ASCII

http://dbslsdb.cpp 4668

B ***LOG BY2=> sql error -4025 performing CON dbds#1 @ 1044 dbds 1044 "

==>

The problem is that you tried to connect as SUPERDBA user, which was created

with Default type < database parameter DEFAULT_CODE=ASCII > & the Application is UNICODE system.

What has to be checked/fixed on your system:

-> Go to TA LC10 -> LCA connection -> Integration && check what user you set for the Standard liveCache user. Why did you set 'SUPERDBA' user ? It has to be SAPR3 or SAP<SID>. Check what

user you selected during the liveCache installation as LCUSER.

-> Please check in LC10 -> Integration for LDA/LEA connections if you set the DBM user - control

& liveCache user and passwords correctly. You could also test connections in /ndb59.

-> For SAP liveCache documentation see the SAP note 767598.

The SAP liveCache documentation in English available for SAP customers at:

http://help.sap.com/saphelp_nw70/helpdata/en/b6/cbdda6248ff648ae9f39f8e28eb24f/frameset.htm

-> Database Administration in CCMS: SAP liveCache Technology

-> liveCache Assistant -> Integration

-> The SUPERDBA user is usually SYSDBA user, see "Brief description of the user types" in the database in the SAP note 25591

-> If you have further problems with liveCache/MAXDB please post them at

MAXDB/liveCache forum:

Thank you and best regards, Natalia Khlopina

[Former Member]

When I run LCA03, I get: Fehler beim anlegen der ORDKEY bzw. ORDMAP Tabellen, or error when creating tables ORDKEY or ORDMAP

[Former Member]

"When I run LCA03, I get: Fehler beim anlegen der ORDKEY bzw. ORDMAP Tabellen, or error when creating tables ORDKEY or ORDMAP"

For someone who's encountering this error, you can disregard this message and continue by going to LCA03 - List - Exit. You should able to see the Analyze livecache and LCA Objects.

Hope it helps to the others.

Regards,

Welmer

[Former Member]

Hello,

What was the solution to this problem, because i am getting the exact same error:

B Wed Apr 01 08:21:25 2009

B Connect to LCA as SAPR3 with tides1-LC1

C Try to connect as SAPR3/<pwd>@tides1-LC1 on connection 1 ...

C Attach to SAP DB : Kernel 7.6.03 Build 008-123-159-187

C Database release is SAP DB 7.6.03.008

C INFO : Database 'LC1' instance is running on 'tides1'

C INFO : LVC DEFAULTCODE = ASCII

C *** ERROR => different codepage: application=UNICODE, LVC=ASCII

Can anyone help?

EDIT: I start a new thread!

EDIT: New thread is here ->

Edited by: Kenneth Nielsen on Apr 1, 2009 9:01 AM

Edited by: Kenneth Nielsen on Apr 1, 2009 9:02 AM

Edited by: Kenneth Nielsen on Apr 1, 2009 9:08 AM

[dorothea_stein]

Hi Kenneth,

if you think that nothing of the above applied or helped in your situation, I recommend to open a CSN ticket with the liveCache folks (BC-DB-LVC).

Best regards,

Dorothea