how can I retrieve 'ign' table

[former_member182034]

Dear All,

I was getting ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found in homogeneous system copy and during system import i skipped that table(SAPSR3.TPALOG) on which ORA-01452 error was occurring mean i just change the 'err' with 'ign' in TSK file. now please tell me how can I retrieve that ignored table(TPALOG).

Regards,

majamil

[Former Member]

Hi,

I would check any file permission issues.

Also if you want you may use SAP Note # 602667 to check validity of the exp. file.

Was the file copied correctly?

[former_member188883]

Hi Majamil,

You can retrieve the table and its contents using the following steps

1) Export the table from source system ( use brtools or exp command )

2) Import the table into target system ( use brtools or imp command ).

Hope this is useful.

Regards,

Deepak Kori

[Former Member]

Hi Deepak,

Because of the same records are exist on the table by the unique key contraints, the system is faced with this error. So, if you export and import the table, the same problem will be occured.

Best regards,

Orkun Gedik

[former_member182034]

sorry to all because i was bizi with system import activities and was getting Check DDIC Password issue. now installation is completed but TPALOG table is missing.

hi Ratnajit,

In the source system , create a workbench transport request(delete the task) and add the Program ID R3TR Object TABL object name TPALOG but doubleclicking the transport request.
 
Import the request into the target system. The table (empty) will be in target system.

Here i am importing the PRD export on Test system and this test system is not the part of Iandscape. I made workbench request on PRD system with program,Object type nd name and this request is not exist in Trans/ CO nd Data folder now how can i transport it on test system.

hi deepakkori,

well gud idea but i will confirm you after do it.

yes my respected Friend Orkun ,

Because of the same records are exist on the table by the unique key contraints, the system is faced with this error. So, if you export and import the table, the same problem will be occured.

Dear, here if i delete primary key TPALOG~0 of table SAPSR3.TPALOG and i try to import this table.

or If i drop the table with following commnad and import it

sql>drop table SAPSR3.TPALOG;

what do you say about above options?

Regards,

[Former Member]

Hi my friend,

sql>TRUNCATE TABLE SAPSR3.TPALOG;

is better way, but don't forget to copy table entries by exporting in a transport request.

Best regards,

Orkun Gedik

[former_member182034]

Dear Orkun,

as per my last reply that i have made workbench request in which i metioned the Program ID R3TR Object type TABL object name TPALOG but this transport request is not exist in trans folder. please let me know that where is this workbench transport is exist on system.

Regards,

[former_member188883]

Hi Majamil,

Please check the following

1) Your workbench request is modifiable ?

2) You have released the workbench request.

If above 2 conditions are met, you will find the transport files in trans directory

Regards,

Deepak Kori

[former_member182034]

Dear Orkun,

I am getting follwing error during table import.

BR0280I BRSPACE time stamp: 2011-12-26 23.34.11
BR0658I List menu 362 - please select one entry
-------------------------------------------------------------------------------
List of BRSPACE exports for import

Pos.  Run           Date                   Tables  Dumps       Size[KB]  Util.

  1 = sehnigrl.tbe  2011-12-26 21.55.41        1      1          11748   EXP
  2 - sedqoohl.tbe  2010-07-11 23.56.09        1      1             58   EXP

Standard keys: c - cont, b - back, s - stop, r - refr, h - help
-------------------------------------------------------------------------------
BR0662I Enter your selection:
1
BR0280I BRSPACE time stamp: 2011-12-26 23.34.16
BR0663I Your selection: '1'

BR1170E Dump file 'G:\oracle\PRD\sapreorg\sehnigrl.edd\expdat.dmp' not found

BR0669I Cannot continue due to previous warnings or errors - you can go back to
repeat the last action

BR0280I BRSPACE time stamp: 2011-12-26 23.34.16
BR0671I Enter 'b[ack]' to go back, 's[top]' to abort:

while expdat.dmp file is exist in mentioned directory.

hi deepak,

I have released following request but this request is not exist in trans/Co nd Data folder while its log exist in Log folder.

Released

    PRDK900047       AJAMIL       HSC: Export Table TPALOG for SI

        Object List of Request

            Table

                TPALOG

        Request Attributes

            SAPCOMPONENT

                IS-H,600,0006
                IS-M,600,0006
                IS-OIL,600,0006
                IS-PS-CA,600,0006
                IS-UT,600,0006
                LSOFE,600,0006
                PI_BASIS,2006_1_700,0015
                SAP_ABA,700,0025
                SAP_AP,700,0025
                SAP_APPL,600,0020
                SAP_BASIS,700,0025
                SAP_BW,700,0027
                SAP_HR,600,0007
                SEM-BW,600,0006
                ST-PI,2005_1_700,0002
                EA-APPL,600,0006
                EA-DFPS,600,0006
                EA-FINSERV,600,0006
                EA-GLTRADE,600,0006
                EA-HR,600,0007
                EA-IPPE,400,0006

Regards,

[volker_borowski2]

Hi,

looks like your PRD system is only configured to create LOCAL transports.

So create a "transport of copies" instead. Select the QAS as the target system.

Second: You need to select the correct entries for the object list

R3TR TABL TPALOG will only transport the table structure. (If the table already exists, you do not need this entry)

R3TR TABU TPALOG will transport the table data (this is most likely what you want)

Volker

[former_member182034]

Dear Volker,

why the Data and Co files of this request is not made in trans folder.

what do you say if I delete/drop this table (sapsr3.TPALOG;) from Test system and then put the Exported file/Transport Request of PRD to Test. here I want to move the table TPALOG with data, so, I will make the request with R3TR TABU TPALOG

Regards,

majamil

[former_member188883]

Hi Majamil,

For your question:

why the Data and Co files of this request is not made in trans folder.

Please check the following

1) Your workbench request is modifiable ?

2) You have released the workbench request.

If above 2 conditions are met, you will find the transport files in trans directory

Regards,

Deepak Kori

[former_member182034]

Dear Deepakkori,

Your workbench request is modifiable ?

after release this tranport request PRDK900047 is showing under Workbench --> Release status.

You have released the workbench request

yes

Regards,

majamil

[volker_borowski2]

> 

> why the Data and Co files of this request is not made in trans folder.

>

> 
> Please check the following
> 1) Your workbench request is modifiable ?
> 2) You have released the workbench request.
> 

and 3) The request is NOT a LOCAL one !

It needs to have a target system assigned.

This is why I suggested a transport of copies instead of a WB request.

Depending on TMS config it might not be possible to assign a target system to a standard WB request,

if no consolidation route exists.

If you like to DROP the table before the import, you need both objects in the transport TABL and TABU.

Best regards

Volker

[former_member182034]

Dear Volker,

thank you very much your support,

Dear All,

BR1170E Dump file 'G:\oracle\PRD\sapreorg\sehnigrl.edd\expdat.dmp' not found

this file(expdat.dmp) exist in mentioned path.

would you tell me about above error and how can i resolve it?

Regards,

majamil

[former_member189725]

In the source system , create a workbench transport request(delete the task) and add the Program ID R3TR Object TABL object name TPALOG but doubleclicking the transport request.

Import the request into the target system.

The table (empty) will be in target system.

[Former Member]

Hi my friend,

What's up??

By the homogeneous system copy you copied the database started it up, successfully., isn't it correct? At which step you faced with this error? This is the DB buffer table for ALOG File. So, it means that there are some records with the same keys in the table during the import. Then, you faced with this error.

Best regards,

Orkun Gedik