client import problem

[Former Member]

Hi,

We have ECC 5.0 / Oracle 10g / RHEL4.0.

We are in the process of importing client in test system

when we execute import command it gives following error plz. help mi

gmt1:gmtadm 34> tp import GMZKT00011 GMT client=100 pf=TP_DOMAIN_GMT.PFL u0126

This is tp version 340.16.70 (release 640, unicode enabled)

Warning: Parameter DBLIBPATH is no longer used.

Warning: Parameter DBSWPATH is no longer used.

This is R3trans version 6.13 (release 640 - 19.01.11 - 17:51:00).

unicode enabled version

2EETW152 Cannot open file "/usr/sap/trans/data/RT00011.GMZ".

: File too large

R3trans finished (0012).

ERROR: stopping on error 12 during MAIN IMPORT

stopping on error 12 during MAIN IMPORT

tp returncode summary:

TOOLS: Highest return code of single steps was: 12

WARNS: Highest tp internal warning was: 0118

tp finished with return code: 12

meaning:

A tool used by tp aborted

regards

[Former Member]

Hi,

Can you please provide details in SLOG.

Regards,

Venkata S Pagolu.

[rupali_karbhari3]

Hi Pradnya,

I would suggest to go through Note 175627 - tp: Test import does not work (load lib)

Adjust the environment of the operating system users that manage the source system and the target system. (This solution does not work for Windows NT.)
              Make sure that the environment variable

                    DIR_LIBRARY

              is set for the operating system users that manage the source and the target system and that it is filled with the correct value. The value must point to the executable directory of the respective system.

              Example: c11adm must have the value /usr/sap/C11/SYS/exe/run for the variable DIR_LIBRARY in its environment.

              Afterwards you must restart both SAP systems (not necessarily directly after you changed the environment, but before you carry out the next step).

              Now, change the configuration of the transport tool using Transaction STMS. To do this, log on to the (Transport Management) domain controller. Start Transaction STMS, branch to the system overview and then to the detail view of your source system. Then maintain the settings of the transport tool. Add a new parameter:

                    dblibpath

              The value for this parameter must remain empty. Otherwise, it would overwrite the settings of the operating system user for DIR_LIBRARY. Make the same setting for the target system. Save and distribute the new settings.

***************

also it shows error as "Unable to open file" , make sure cofiles and datafile permission is correct so as to allow to import

Thanks,

[Former Member]

my error is unable to open file : file too large

[rupali_karbhari3]

Hi Pradnya,

According to SAP note Note 546006 - Problems with Oracle due to operating system errors

If data files are affected, check in the Oracle alert log whether errors occurred with a RESIZE or with an AUTOEXTEND. If you do find errors there, investigate them further.

Otherwise, check your hardware using the command. Using

  SELECT BYTES FROM V$DATAFILE WHERE NAME = '<datafile>'; 

              you can check if the file size Oracle expects is the same as the actual existing data file at operating system level. The size of the data files at operating system level must always be 8192 bytes bigger than the value in V$DATAFILE. If required, restore the affected data files from a good backup and recover them.

*************

In addition to above check Note 553854 - Oracle: Problems with file size limit

Data file: Specify a file size that is smaller than the limit on the operating system.

   If you have questions about the maximum file size permitted at operating system level, contact your hardware partner. Notes 129439 and 20823 may also provide you with useful information about individual operating systems.

Best Regards,