Import running for a long time

[former_member952456]

Hi Experts,

In STMS req is running for a long time , i checked TP SYSTEM LOG it is saying that " Background job RDDIMPDP could not be started or terminated abnormally " in SM37 it is getting cancelled ,

Please help me it is running since 12 Hrs.

Regards

Mohammed

[Former Member]

Hi Mohammed,

Check RDDIMPDP is running properly on SM37 logs. The job user might be locked. Additionally, paste the dev_tp under work dir, to find out the details.

Best regards,

Orkun Gedik

[former_member952456]

Hi Orkun ,

In SM37 there is no log just it is showing CANCELLED,

DEV_TP

This is R3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).

unicode enabled version

R3trans finished (0000).

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBLIBPATH is no longer used.

Warning: Parameter DBNAME is no longer used.

Warning: Parameter DBSWPATH is no longer used.

tp finished with return code: 0

meaning:

  Everything OK

The import of the transport request JD1K908941 for system JD1 was not performed.

Please check the tp command. The buffer entry is printed out below.

JD1 buffer:

JD1K908941          |                    | |will not be imported because it is already in the system.

TASK                |PROJECT             |P|CMD I |DD Im |Activ |MainI |MC Ac |ADO I |VersF |XPRA  |Gener |UMODE|TAGS

--------------------+--------------------+-+------+------+------+------+------+------+------+------+------+-----+----

No valid entry found for JD1K908941 in JD1 buffer.

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

SWARNS: Highest tp internal severe warning was: 0152

tp finished with return code: 0

meaning:

  Everything OK

This is R3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).

unicode enabled version

R3trans finished (0000).

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBLIBPATH is no longer used.

Warning: Parameter DBNAME is no longer used.

Warning: Parameter DBSWPATH is no longer used.

tp finished with return code: 0

meaning:

  Everything OK

This is R3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).

unicode enabled version

R3trans finished (0000).

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBLIBPATH is no longer used.

Warning: Parameter DBNAME is no longer used.

Warning: Parameter DBSWPATH is no longer used.

tp finished with return code: 0

meaning:

  Everything OK

This is R3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).

unicode enabled version

R3trans finished (0000).

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBLIBPATH is no longer used.

Warning: Parameter DBNAME is no longer used.

Warning: Parameter DBSWPATH is no longer used.

tp finished with return code: 0

meaning:

  Everything OK

This is R3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).

unicode enabled version

R3trans finished (0000).

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBLIBPATH is no longer used.

Warning: Parameter DBNAME is no longer used.

Warning: Parameter DBSWPATH is no longer used.

tp finished with return code: 0

meaning:

  Everything OK

This is R3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).

unicode enabled version

R3trans finished (0000).

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBLIBPATH is no longer used.

Warning: Parameter DBNAME is no longer used.

Warning: Parameter DBSWPATH is no longer used.

tp finished with return code: 0

meaning:

  Everything OK

This is R3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).

unicode enabled version

R3trans finished (0004).

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBLIBPATH is no longer used.

Warning: Parameter DBNAME is no longer used.

Warning: Parameter DBSWPATH is no longer used.

tp finished with return code: 0

meaning:

  Everything OK

This is R3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).

unicode enabled version

R3trans finished (0000).

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBLIBPATH is no longer used.

Warning: Parameter DBNAME is no longer used.

Warning: Parameter DBSWPATH is no longer used.

tp finished with return code: 0

meaning:

  Everything OK

This is R3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).

unicode enabled version

R3trans finished (0000).

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBLIBPATH is no longer used.

Warning: Parameter DBNAME is no longer used.

Warning: Parameter DBSWPATH is no longer used.

tp finished with return code: 0

meaning:

  Everything OK

This is R3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).

unicode enabled version

R3trans finished (0000).

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBLIBPATH is no longer used.

Warning: Parameter DBNAME is no longer used.

Warning: Parameter DBSWPATH is no longer used.

tp finished with return code: 0

meaning:

  Everything OK

This is R3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).

unicode enabled version

R3trans finished (0000).

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBLIBPATH is no longer used.

Warning: Parameter DBNAME is no longer used.

Warning: Parameter DBSWPATH is no longer used.

tp finished with return code: 0

meaning:

  Everything OK

This is R3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).

unicode enabled version

R3trans finished (0000).

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBLIBPATH is no longer used.

Warning: Parameter DBNAME is no longer used.

Warning: Parameter DBSWPATH is no longer used.

tp finished with return code: 0

meaning:

  Everything OK

[Former Member]

Hi,

Can you check is any lock is there in SM12 ?

The tp log is normal and we can't see any abnormalities also check the SM21 log.

[Former Member]

Check whether the job user is locked on SM37? Additionally, you can execute the RDDNEWPP on SE38 and update the job.

[former_member952456]

Hi ,

this is sm21 log

Details   Page 2 Line 6 System Log: Local Analysis of jprod                     1

Time

Ty.

Nr

Cl.

User

Tcod

MNo

Text                                                                    Date : 10.10.12

10:01:06

BTC

028

551

RNANDYALA

R38

Error at DB commit, return code 001024

D

etails

Recording   at local and central time........................ 10.10.2012 10:01:06

Task................   27623  /  Background Processor No. 28

User................   RNANDYALA

Client..............   551

Terminal............

Session.............   1

Transaction   code....

Program   name........ MP200000

Problem   class....... K    SAP Web AS Problem

Development   class... STSK

Further details for   this message type

Module   name......... thxxhead

Line................   1214

Error   text..........  001024

Caller..............   ThIComm

Reason/called.......   db_comm

Documentation for   system log message R3 8 :

Database commit   failed.  Check whether there are   problems at the

database level.

T

echnical details

File................   023870

Position............   0000354960

Entry   type.......... m      ( Error   (Function,Module,Row)    )

Message   ID.......... R3 8

Variable   parts......  001024                                ThICommdb_commthxxhead1214

[former_member952456]

Hi ,

User is unlocked but still it is getting cancelled , i checked in SM21 i got this """ Error at DB commit, return code 001024 """

Regards

Mohammed

[former_member952456]

No lock entries found

[Former Member]

Could you check dev_<xx> trace files (regarding your syslog entry check dev_w28) on ST11 and alert_<SID>.log?

Best regards,

Orkun Gedik

[former_member952456]

Dear Sir,

This is output of datafiles SAPDATA 4 is showing 100% full , please let me know where i can check alert.SID ?

/dev/dsk/c1t0d0s6       44G    21G    23G    48%    /dumps

/dev/md/dsk/d3         9.9G   1.9G   7.8G    20%    /oracle

/dev/md/dsk/d63         15G   2.3G    12G    16%    /sapmnt/JP1

/dev/md/dsk/d64         15G   7.7G   6.9G    53%    /usr/sap

/dev/md/dsk/d61        4.9G   762M   4.1G    16%    /oracle/JP1/saptrace

/dev/md/dsk/d62        4.9G   6.8M   4.9G     1%    /oracle/JP1/sapbackup

/dev/md/dsk/d60        4.9G   2.4G   2.5G    50%    /oracle/JP1/920_64

/dev/md/dsk/d66        963M   201M   704M    23%    /oracle/JP1/origlogB

/dev/md/dsk/d72         53G   9.8G    42G    19%    /oracle/JP1/sapdata2

/dev/md/dsk/d70        963M    41M   864M     5%    /oracle/JP1/saparch

/dev/md/dsk/d69        963M   201M   704M    23%    /oracle/JP1/mirrlogA

/dev/md/dsk/d67        963M   208M   698M    23%    /oracle/JP1/origlogA

/dev/md/dsk/d71         53G    20G    32G    38%    /oracle/JP1/sapdata1

/dev/md/dsk/d73         53G    26G    26G    50%    /oracle/JP1/sapdata3

/dev/md/dsk/d74         53G    52G    20M   100%    /oracle/JP1/sapdata4

/dev/md/dsk/d65        9.8G    59M   9.7G     1%    /usr/sap/trans

/dev/md/dsk/d68        963M   201M   704M    23%    /oracle/JP1/mirrlogB

/dev/md/dsk/d4          15G   3.5G    11G    24%    /oracle/JP1/oraarch

/export/home/jp1adm     24G   8.1G    16G    35%    /home/jp1adm

/vol/dev/dsk/c5t0d0/unnamed_rmdisk:c

Regards

Mohammed

[former_member952456]

Shall I delete DEV_wXX.old file ?

[Former Member]

To find alert log, execute the statement, below;

SQL> show parameter background

The statement will provide the "alert_<SID>.log" path.

On the other hand, you need to find out why the sapdata4 is used 100%. Deleting dev*.old trace files will reclaim the storage, if sapdata4 and work directories are located on the same logical volume.

Best regards,

Orkun Gedik

[former_member952456]

Hi ,

Alert.log is too large i cannot paste it here , and WORK dir and SAPDATA4 is in different volumes.

how to and SAPDATA4 is in AUTO extend mode.

regards

[former_member952456]

Hi ,

in SM21 i found this message,Please help me

SL ST0

____________________________________________________

Short Text

No free memory available in class &5. Memory block ID "&6", &9
bytes.

The storage request of the given storage class cannot be
fulfilled.

Possible causes:

For the storage classes ROLL and SHORT the profile defaults are not
sufficient, or the storage areas are inconsistent.
The operating system
cannot request storage for storage classes PERM and TASK.

Regards

Mohammed

[Former Member]

>> Shall I delete DEV_wXX.old file ?

You can delete *.old files, safely, but it will not change the situation. Furthermore, You should identify why the RDDNEWPP job is cancelled, to solve the problem.

Best regards,

Orkun Gedik

[former_member952456]

Hi ,

this might be because files system full , i mean SAPDATA4 showing 100 % , how to extedend and it is showing AUTO extend mode.

Best Regards

Mohammed

[Former Member]

>> Alert.log is too large i cannot paste it here , and WORK dir and SAPDATA4 is in different volumes.

But, you said that the work and sapdata4 volumes are different. You can monitor error in the database alert log, if the tablespace is full. Execute the command, below to see the freespace usage on tablespaces;

brspace -u / -f dbshow -c tsinfo

On the other hand, if the datafiles are in the autoextend mode the datafile will be extended, automatically. So, check the freespace I noted above.

Best regards,

Orkun Gedik

[former_member952456]

Dear Sir,

Output od brspace , please suggest me ,

by the way transport requests are importing now , but i want to solve this issue please help .

Best regards

Mohammed

[Former Member]

Regarding to the picture, you should add datafiles to the PSAPJP1 and PSAPTEMP, with commands, below;

SQL> alter tablespace <tablespace_name> add datafile '/oracle/<DBSID>/sapdata<n>/<datafile_path>/<datafilename> size <initial_tablespace_size>M autoextend on next <initial_extend_size>M maxsize <max_tablespace_size>M;

Or you can add datafile by using brtools which is recommended option.

Best regards,

Orkun Gedik