NW2004S Unicode Conversion

[Former Member]

I am trying to do a homogenous copy and unicode version of a NW2004S

abap stack. I followed the directions in the NW2004S SP11 Unicode

conversion guide. The copy/conversion fails on the step where it

attempts to create new nametabs:

WARNING 2007-05-21 13:36:13

Execution of the command "\usr\sap\BWD\SYS\exe\run\dipgntab -rwr40 -

srctt DDNTT -srctf DDNTF -dsttt DDNTT -dsttf DDNTF -ttonly TT" finished

with return code 11. Output:

/usr/sap/BWD/SYS/exe/run/dipgntab=>sapparam(9): environment variable

$SAPSYSTEM format error.

-

---

Begin: NAMETAB OPERATION rewrite of active nametabs ("20070521133520")

-

---

PARAMETERS FOR NAMETAB OPERATION "read/write of active NT (for NT

switch)" :

SOURCE NAMETAB (HEADER TABLE) = DDNTT

SOURCE NAMETAB (FIELDS TABLE) = DDNTF

DEST. NAMETAB (HEADER TABLE) = DDNTT

DEST. NAMETAB (FIELDS TABLE) = DDNTF

OPTION = TT

LIST-TABLE OF TABLENAMES = <NOT SET>

TABLENAME FIELD IN LIST-TABLE = <NOT SET>

START RELEASE (in cp/cmp NT) = <NOT SET>

DEST. RELEASE (in cp/cmp NT) = <NOT SET>

EXTENSION (in cp/cmp NT only) = <NOT SET>

WCONTENT (in cp/cmp NT) = <NOT SET>

FLAGS (in cp/cmp NT) = <NOT SET>

-

---

-

---

Didb-lib Version : 1.3

OPTIONS:

PRINT ONLY = no

iNT-TIMESTAMP RESET = no

DELETE iNT = yes

DELETE iNT FIELDS = yes

ACTIVATE iNT = yes

TOLERATE UNCRITICAL STMTs = no

COMPARE TIMESTAMPs IN MV40-Op. = yes

SUPPRESS COMMITs = no

CALL EXTERNAL NT_SYNC = no

DONT TOUCH dep. LOADS = no

RESET FLAG DBTABPOS = no

protocol output to file = no (NULL)

-

---

rewrite nt "/BI0/ABP_ID00":

ERROR 2007-05-21 13:36:13

CJS-30023 Process call '\usr\sap\BWD\SYS\exe\run\dipgntab -rwr40 -

srctt DDNTT -srctf DDNTF -dsttt DDNTT -dsttf DDNTF -ttonly TT' exits

with error code 11. For details see log file(s) dipgntab.log.

ERROR 2007-05-21 13:36:13

FCO-00011 The step adjustNametab with step key

|NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_DB4|ind|ind|ind|ind|4|0|adjustNametab was executed with

status ERROR .

INFO 2007-05-21 13:36:30

An error occured and the user decide to stop.\n Current

step "|NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_DB4|ind|ind|ind|ind|4|0|adjustNametab".

I have checked tables the following tables on the database level

(Iseries)...DDNTF, DDNTT, DDNTT_CONV_UC, DDNTF_CONV_UC all have data

and all the DDX* tables are empty. Also the kernel has been updated to

the most current patches available as of a week ago.

I have read through the Unicode conversion troubleshooting guide but

found nothing to assist me with this issue. The environment variable

SAPSYSTEMNAME=<sid> is present as well.

Thank you for your assistance.

Doug

[markus_doehr2 · Accepted solution]

Is this during the import? Are you using the latest R3load and dipgntab? (it's not in the latest kernel but a separate patch)

Was RADCUCNT ran successfully in the exporting system?

If this is all the latest versions I'd open an OSS call.

--

Markus

[Former Member]

Hi,

I have the same problem. To solved the problem.

1. Stop the installation.

2. Patch the kernel, DW and lib_dbsl to latest available kernel.

3. Continue the installation again

Regards,

[former_member195641]

BTW, I mean with "running dipgntab manually" calling the program on the OS/400 command line as user BWDOFR with exact the same parameters as the SAPinst did. By doing this I saw the core dump. cU, René

[former_member195641]

Hi Doug,

bad news. Your system installation is not complete. I checked the logfiles of SAPinst and missed some necessary steps. Therefore, dipgntab fails as well with a core dump which is recognized by SAPinst as an error.

I updated the customer message which should be used from now as the only one thread. Next week I'm out for vacation, so I informed my colleagues to handle your customer message directly.

Best regards,

René

[Former Member]

Good morning Rene,

I updated the OSS ticket with the information you requested. I am unsure what you mean though by running DIPGNTAB again.

Regards,

Doug

[former_member195641]

... and please tell me if it would be okay for you running DIPGNTAB manually. I want to see the content of the joblog. Make a notice into the customer message about this.

Regards, René

[former_member195641]

Hi Goug,

your customer message has been updated. Please have a look.

Regards, René

[former_member195641]

Hi Doug,

having these both tables in SAPSDIC.STR (hopefully among with other tables) we can be sure that probably missing tables in the STR files is

not

the reason and you did

not

hit the problem with the buggy R3LDCTL.

The reason must be an other one. I will have a look at it.

Regards, René

[Former Member]

Hello Rene,

Here is some information from the SAPSDIC.STR file after I ran the R3LDCTL command in the ascii system. I am just copying the information for the two tables you listed:

tab: DDNTF

att: SDIC 4 ?? N all DDNTF~0 SDIC 4

fld: TABNAME CHAR 30 0 0 not_null 1

fld: BLOCKNR INT1 1 0 0 not_null 2

fld: FIELDSLG DEC 3 5 0 not_null 0

fld: FIELDS LRAW 0 0 0 null 0

tab: DDNTT

att: SDIC 3 ?? T all DDNTT~0 SDIC 3

fld: TABNAME CHAR 30 0 0 not_null 1

fld: VERSION CHAR 1 0 0 not_null 0

fld: UUID RAW 16 0 0 null 0

fld: CRTIMESTMP CHAR 14 0 0 not_null 0

fld: ABTIMESTMP CHAR 14 0 0 not_null 0

fld: DYTIMESTMP CHAR 14 0 0 not_null 0

fld: FLDCNT INT2 2 0 0 not_null 0

fld: TABLENGTH INT4 4 0 0 not_null 0

fld: KEYCNT INT1 1 0 0 not_null 0

fld: KEYLENGTH INT2 2 0 0 not_null 0

fld: CLIENTPOS INT1 1 0 0 not_null 0

fld: TABTYPE CHAR 1 0 0 not_null 0

fld: TABFORM CHAR 1 0 0 not_null 0

fld: REFNAME CHAR 30 0 0 not_null 0

fld: HFLAG RAW 6 0 0 null 0

fld: BUFSTATE CHAR 1 0 0 not_null 0

fld: BUFPARM INT2 2 0 0 not_null 0

fld: ALIGN INT1 1 0 0 not_null 0

fld: POINTERLG INT1 1 0 0 not_null 0

fld: UNICODELG INT1 1 0 0 not_null 0

fld: COMPCNT INT2 2 0 0 not_null 0

fld: LEAFCNT INT2 2 0 0 not_null 0

I also have a SAP OSS ticket open, and our system is open through the SAP OSS site for access.

Thank you kindly for your assistance,

Doug

[former_member195641]

Hi Goug,

it does not make any sense to run the same commands with Unicode programs against an ASCII database. Both databases are similar but not really compatible. Running the commands against a Unicode database should produce also the control files (they are necessary e.g. for a homogeneous system copy of a Unicode system).

How the SAPSDIC.STR file looks like? Can you find all the nametab tables in it (tables with name DD*, especially DDNTT and DDNTF)?

If still in trouble you should open Telnet that we can have a look.

Regards, René

[Former Member]

Hello Rene,

I appreciate sincerely the last reply and hints you gave. I tested the R3LDCTL in the ascii system per your instructions and it ran flawlessly and generated all the files you mentioned. Next I tried the same commands in the unicode system I am trying to build and it stopped with an error:

(DDL) ERROR: Unknown DDIC type "0" for field in table APSRV

Error occurs for field .

Error occurs for table APSRV.

Thank you,

Doug

[former_member195641]

Hi Doug,

report RADCUCNT needs to run again if something has been changed in between (e.g. if the system was running after the first run and Unicode nametab elements have changed). If you are sure that no Unicode nametab relevant changes happened in between the run using SPUMG should be sufficient.

For the file SAPSDIC.STR, I cannot provide a complete path since it depends on the SAPinst version and the involved SAP product. But it is quite easy to find it starting in directory /usr/sap/SAPinst. Just open a Windows share on your iSeries box, go to this directory and let the Windows explorer search for it. The file itself appears first when the export was started and the step with R3LDCTL has been passed.

If unsure if you have the right version of R3LDCTL you can test it easily in front of an export.

1. Signon as user

5. R3ldctl <-- here the ASCII version is required !

Afterwards, you can find all *.STR and *.TPL files needed for the export in this temporary directory, and SAPSDIC.STR as well.

Best Regards,

René

[Former Member]

Rene,

Thank you very much for the reply. I will double check for updates for the non unicode kernel and update if need be, The unicode kernel is very up to date and the R3INLPGM is indeed in the kernel library as well as the R3<SID>400 library and the files match each other for creation date.

One thing I did not do is run RADCUCNT from SE38 with those variants. I ran this from SPUMG with the create unicode nametabs menu selection and the report displayed no errors that I am aware of.

Lastly, I am not quite sure where to locate the SAPSDIC.STR file. If you could enlighten me where it is located I would sincerely appreciate it.

Thank you again for your assistance.

Regards,

Doug Slupski

[former_member195641]

Hello Doug,

reading these messages, 2 things came into my mind:

1. SAP note 918335

There is a known issue with the R3LDCTL program in the ASCII (!!!) kernel since the necessary control files for export/import are written from programs in the ASCII kernel. Unfortunately the bug occurs first after the reload of the database. Please check if your SAPSDIC.STR contains the entries for the dictionary tables.

2. The issue with "$SAPSYSTEM format error"

Please check if you have the latest version of R3INLPGM in both kernels ASCII and Unicode and corresponding in library R3400. The version in the 3rd library has to be identically with the one from the SAP kernel that is currently applied to the system.

Just a hint right at the end, please follow the guides as close as possible. Especially report RADCUCNT can have some impact and running it again (with the right variant name) might be possible. For details please have a look at SAP note 837173.

Best regards,

René Lang

SAP NetWeaver on IBM System i Development

[Former Member]

Markus,

Thank you for the reply. First, I have patched the R3load, R3trans, libdbsl, DW, r3ldctl, Rtvenvvar, among other things. I am not quite sure how to apply the patch for dipgntab as it is not listed and I am unsure as to what patch it would be included in.

While I did not run RADCUCNT directly from SE38, I did execute Create Unicode nametabs from within SPUMG and there were not any errors after that had ran that I noticed.

I also did find the same note 937983 and ran the DIPGNTAB '-rwr40 -srctt DDNTT -srctf DDNTF -dsttt DDNTT -dsttf DDNTF -ttonly TT' on the operating system level before I executed the unicode preconversion routine in the SID I am attempting to convert. I just tried to process this very same command on the newly created unicode SID and received the very same error the sapinst gave me.

I also have a message out to SAP on this issue.

Thank you again for the assistance.

Doug

[markus_doehr2]

Thanx a lot for the update... I have no further idea

We did an UC-conversion also, see here (my long post):

We have had nametab trouble too - but not in BI related tables...

--

Markus

[markus_doehr2]

Also check note 937983 which describes a problem with field sequence selections caused by a wrong libdbsl.

--

Markus

[Former Member]

Hello Volker,

Thank you for responding. Here is everything that is in the dipgntab.log:

/usr/sap/BWD/SYS/exe/run/dipgntab=>sapparam(9): environment variable $SAPSYSTEM format error.

-

---

Begin: NAMETAB OPERATION rewrite of active nametabs ("20070521133520")

-

---

PARAMETERS FOR NAMETAB OPERATION "read/write of active NT (for NT switch)" :

SOURCE NAMETAB (HEADER TABLE) = DDNTT

SOURCE NAMETAB (FIELDS TABLE) = DDNTF

DEST. NAMETAB (HEADER TABLE) = DDNTT

DEST. NAMETAB (FIELDS TABLE) = DDNTF

OPTION = TT

LIST-TABLE OF TABLENAMES = <NOT SET>

TABLENAME FIELD IN LIST-TABLE = <NOT SET>

START RELEASE (in cp/cmp NT) = <NOT SET>

DEST. RELEASE (in cp/cmp NT) = <NOT SET>

EXTENSION (in cp/cmp NT only) = <NOT SET>

WCONTENT (in cp/cmp NT) = <NOT SET>

FLAGS (in cp/cmp NT) = <NOT SET>

-

---

-

---

Didb-lib Version : 1.3

OPTIONS:

PRINT ONLY = no

iNT-TIMESTAMP RESET = no

DELETE iNT = yes

DELETE iNT FIELDS = yes

ACTIVATE iNT = yes

TOLERATE UNCRITICAL STMTs = no

COMPARE TIMESTAMPs IN MV40-Op. = yes

SUPPRESS COMMITs = no

CALL EXTERNAL NT_SYNC = no

DONT TOUCH dep. LOADS = no

RESET FLAG DBTABPOS = no

protocol output to file = no (NULL)

-

---

rewrite nt "/BI0/ABP_ID00":

Thank you,

Doug

[Former Member]

Hi Doug,

OK, I thought that already ... not very helpful ...

Sorry,

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

Hi Doug,

do we see here the DIPGNTAB.log as well or is this one missing ?

(something similar seems to be there in the middle)

Because I would hope on more information there ...

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de