Skip to Content
author's profile photo Former Member
Former Member

DB6CONV source and target table organization must be specified!

Hi

Im facing some strange case when using DB6CONV. I have used DB6CONV tools several time to move table from one tablespace to another, so far i never get any problem.

I want to move table TTREET (and several other tables) from tablespace ES700D & ES700I to target tablespace ES731D & ES731I

But in one of my server, the conversion are not running :

20160901 100124 =============NEW CONVERSION - START==================

20160901 100124 Version of DB6CONV : 6.30

20160901 100124 SID : D01

20160901 100124 Name of application server : xxxxxx

20160901 100124 strt_date,strt_time : 20160901 100124

20160901 100124 Starttime : 20160901 100124

20160901 100124 Internal Conversion ID : 12

20160901 100124 Conversion type : Batch immediate

20160901 100124 >> Batch job name : DB6CONV_TTREET

20160901 100124 >> Batch job number : 10012400

20160901 100124 Conversion defined specifying : Target Data Class

20160901 100124 Conversion object : Single Table

20160901 100124 Table name : TTREET

20160901 100124 Data Class : SSEXC

20160901 100124 DATA Tablespace (from TADB6) : D01#ES731D

20160901 100124 >>> Partition group : SAPNODEGRP_D01

20160901 100124 >>> Partition number : 0

20160901 100124 INDEX Tablespace (from IADB6) : D01#ES731I

20160901 100949 >>> Partition group : SAPNODEGRP_D01

20160901 100949 >>> Partition number : 0

20160901 100949 LONG Tablespace (optional) :

20160901 100949 Use COPY_WITH_INDEXES : Yes

20160901 100949 Use LOAD : No

20160901 100949 Use REDIRECT : No

20160901 100949 Stop before switching : No

20160901 100949 Switch on AMT Trace : No

20160901 100949 COMPRESS Data : KEEP

20160901 100949 COMPRESS Index : KEEP

20160901 100949 ITC : Keep

20160901 100949 Delete original : Yes

20160901 100949 Update Statistics After Conv. : Yes

20160901 100949 Source Table Organization : Row

20160901 100949 Target Table Organization :

20160901 100949 ***************************************************

CONVERSION NOT STARTED YET !

20160901 100949 Conversion is not possible; source and target table organization must be

specified!

20160901 100949 Source table organization from DB6CONVT: 'R'

20160901 100949 Target table organization from DB6CONVT: ''

____________________________________________________________________________________________________

I execute the same task in another server, but didnt get error. I compare the log with log from another server and i found that the Target table organization from DB6CONVT: '' should be R, but in this server, the value are empty, thus the conversion didnt run.

Please help, did anybody ever face the same problem? Or is it some bug on DB6CONV?

regards

Andreas

log.png (42.0 kB)
selection.png (24.6 kB)
Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Sep 01, 2016 at 08:57 AM

    hi andreas,

    one additional question: you screenshots show for the same(!) table

    - in system 1: source table organization = 'R', target organization = 'R' -> conversion works

    - in system 2: source table organizaion = 'R', target organization = '' -> conversion not possible

    i need to understand the differences of the systems.
    did you plan/define the conversion from scratch in both systems? or did you (for example)

    plan the conversion in system 2 with a db6conv version <6.30 and start it with V6.30?

    if the scenario (source = 'R', target = '') was exclusively done with V6.30, please open a SAP incident and open the system connection, so i can analyze and debug. please tell me the incident number.

    best regards, frank

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Frank-Herwig Walter

      Hi Frank

      I've try DB6CONV 6.31 but i got different error :

      1. I cannot do a reset for job with status aborted.

      2. The conversion still failed with this error :

      20160902 092914 =============NEW CONVERSION - START==================

      20160902 092914 Version of DB6CONV : 6.31

      20160902 092914 SID : D01

      20160902 092914 Name of application server : sapfdv01

      20160902 092914 strt_date,strt_time : 20160902 092914

      20160902 092914 Starttime : 20160902 092914

      20160902 092914 Internal Conversion ID : 18

      20160902 092914 Conversion type : Batch immediate

      20160902 092914 >> Batch job name : DB6CONV_TTREEP

      20160902 092914 >> Batch job number : 09291400

      20160902 092914 Conversion defined specifying : Target Data Class

      20160902 092914 Conversion object : Single Table

      20160902 092914 Table name : TTREEP

      20160902 092914 Data Class : SSEXC

      20160902 092914 DATA Tablespace (from TADB6) : D01#ES731D

      20160902 092914 >>> Partition group : SAPNODEGRP_D01

      20160902 092914 >>> Partition number : 0

      20160902 092914 INDEX Tablespace (from IADB6) : D01#ES731I

      20160902 092914 >>> Partition group : SAPNODEGRP_D01

      20160902 092914 >>> Partition number : 0

      20160902 092914 Use COPY_WITH_INDEXES : Yes

      20160902 092914 Use LOAD : No

      20160902 092914 Use REDIRECT : No

      20160902 092914 Stop before switching : No

      20160902 092914 Switch on AMT Trace : No

      20160902 092914 COMPRESS Data : KEEP

      20160902 092914 COMPRESS Index : KEEP

      20160902 092914 ITC : Keep

      20160902 092914 Delete original : Yes

      20160902 092914 Update Statistics After Conv. : Yes

      20160902 092914 Source Table Organization : Row

      20160902 092914 Target Table Organization : Row

      20160902 092914 ***************************************************

      20160902 092914 ONLINE CONVERSION: Start of Step 0

      20160902 092914 Data Class of original table : SSEXC

      20160902 092914 Data Tablespace of original table : D01#ES700D

      20160902 092914 >>> Partition group : SAPNODEGRP_D01

      20160902 092914 >>> Partition number : 0

      20160902 092914 Index Tablespace of original table: D01#ES700I

      20160902 092914 >>> Partition group : SAPNODEGRP_D01

      20160902 092914 >>> Partition number : 0

      20160902 092914 Long Tablespace of original table : <not defined>

      20160902 092914 Cardinality of original table : 436432

      20160902 092914 Pagesize of original tablespaces : 16384 Byte

      20160902 092914 Pagesize of target tablespaces : 16384 Byte

      20160902 092914 Create Time : 2013-05-08 11:26:22.356733

      20160902 092914 Volatile : No

      20160902 092914 Table Compression : B

      20160902 092914 Row Compression Mode : S

      20160902 092914 Clustered : N

      20160902 092914 Size of table TTREEP

      20160902 092914 >>> Database Partition: 0

      20160902 092914 >>> Data Partition : 0

      20160902 092914 >>> Total Size [KB]: 27136

      20160902 092914 >>> Data Size [KB] : 13376

      20160902 092914 >>> Long Size [KB] : 0

      20160902 092914 >>> LOB Size [KB] : 0

      20160902 092914 >>> Index Size [KB]: 13760

      20160902 092914 >>> Dict. Size [B] : 84224

      20160902 092914 >>> PCTPAGESSAVED : 70

      20160902 092914 Describe Table TTREEP

      20160902 092914 >>> (colno, colname, typename, length, scale, nulls, codepage,

      inline_length, pctinlined, hidden)

      20160902 092914 >>> ----------------------------------------------------------

      20160902 092914 >>> 0 ID VARCHAR 96 0 N 1208 0 1- ''

      20160902 092914 >>> 1 EXTENSION VARCHAR 45 0 N 1208 0 1- ''

      20160902 092914 >>> 2 COUNTER INTEGER 4 0 N 0 0 1- ''

      20160902 092914 >>> 3 PARAM_ID VARCHAR 30 0 N 1208 0 1- ''

      20160902 092914 >>> 4 PARAM_VAL VARCHAR 180 0 N 1208 0 1- ''

      20160902 092914 >>> 5 PARAM_VAL2 VARCHAR 180 0 N 1208 0 1- ''

      20160902 092914 Indexes of Table TTREEP (schema <> 'SYSIBM')

      20160902 092914 >>> (indname, uniquerule, indextype, compression, reverse_scans,

      fullkeycard, colnames)

      20160902 092914 >>> -------------------------------------------------------

      20160902 092914 >>> TTREEP~0 P REG Y Y 436432 +ID+EXTENSION+COUNTER

      20160902 092914 >>> TTREEP~PAR D REG Y Y 32477 +PARAM_ID+PARAM_VAL

      20160902 092914 DDIC-tableclass : TRANSP

      20160902 092914 No STATISTICS_PROFILE found

      20160902 092914 No REMARKS found

      20160902 093001 =============RESET CONVERSION - START================

      20160902 093001 Version of DB6CONV : 6.31

      20160902 093001 Starttime : 20160902 093001

      20160902 093001 Tablename : TTREEP

      20160902 093001 ***************************************************

      20160902 094212 =============RESET CONVERSION - START================

      20160902 094212 Version of DB6CONV : 6.31

      20160902 094212 Starttime : 20160902 094212

      20160902 094212 Tablename : TTREEP

      20160902 094212 ***************************************************

      I already open sap incident and connection to this server. Hope we can find the solution.

      thank you for your help

      regards

      Andreas

  • Posted on Sep 01, 2016 at 07:31 AM

    Hi Andreas,

    this i a bug in DB6CONV, that was introduced with V6.30 . V6.31, that will be released today or tomorrow, will fix this. the error will be documented in sap note 1513862 then as well.

    best regards, Frank

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 07, 2016 at 09:16 AM

    Problem solved after upgrade to DB6CONV 6.32.

    regards

    Andreas

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.