Problem to capture tables in Sybase 12.5 database

Hello,
I try to capture objects from a sybase database in Designer 9.0.4 with ODBC, the connection run properly in the Design Editor tool's, Capture Design Of Server Model, nobody objects appears.
Thanks for yours responses.

Run correctly if you choice ANSI 92 against Sybase!
I have always a problem when I capture tables selected nothing happens, I'm not sure if Designer can capture objects provide by sybase > V11

Similar Messages

Problem creating schema/tables on sybase

Running the schematool or using the SynchronizeSchema feature, I get the
following exception on sybase:
com.sybase.jdbc.SybSQLException: The 'CREATE TABLE' command is not allowed
within a multi-statement transaction in the 'MEDIA' database.
The same application deploys fine using SQL-server or Oracle.
I'm using kodo 2.4.0.
Any ideas?
Detailed exception included in attachment.
Regards
Jesper
begin 666 exception.txt
M<V-H96UA=&]O;#H-"EMS8VAE;6%T;V]L72 H:V]D;RY2=6YT:6UE(" @(" @
M(" @(" @(" @(" @(" @(" @,3,U("D@4W1A<G1I;F<@2V]D;R!*1$\@=F5R
M<VEO;B R+C0N," H:V]D;VID;RTR+C0N,"TR,# R,3(Q,BTQ-S,P*2!W:71H
M(&-A<&%B:6QI=&EE<SH@6T5N=&5R<')I<V4@161I=&EO;B!&96%T=7)E<RP@
M4W1A;F1A<F0@161I=&EO;B!&96%T=7)E<RP@3&ET92!%9&ET:6]N($9E871U
M<F5S+"!1=65R>2!%>'1E;G-I;VYS+"!$871A8V%C:&4@4&QU9RUI;BP@4W1A
M=&5M96YT($)A=&-H:6YG+"!';&]B86P@5')A;G-A8W1I;VYS+"!$979E;&]P
M97(@5&]O;',L($-U<W1O;2!$871A8F%S92!$:6-T:6]N87)I97,L($5N=&5R
M<')I<V4@1&%T86)A<V5S70T*6W-C:&5M871O;VQ=("AK;V1O+DUE=&%$871A
M(" @(" @(" @(" @(" @(" @(" @(" X-B @*2!C;VTN<V]L87)M971R:6,N
M:V]D;RYM971A+DI$3TUE=&%$871A4&%R<V5R0&$X,V$Q,SH@<&%R<VEN9R!S
M;W5R8V4Z(&9I;&4Z1#HO8FQA8VMW:61O=R]W;W)K87)E82]E;F%C=&UE;G0O
M8G5I;&0O8VQA<W-E<R]D:R]P:6YE+V5N86-T;65N="]S97)V:6-E<R]087)A
M;65T97)$969,:7-T+FID;PT*6W-C:&5M871O;VQ=("AK;V1O+DUE=&%$871A
M(" @(" @(" @(" @(" @(" @(" @(" X-B @*2!C;VTN<V]L87)M971R:6,N
M:V]D;RYM971A+DI$3TUE=&%$871A4&%R<V5R0#=C9#,W83H@<&%R<VEN9R!S
M;W5R8V4Z(&9I;&4Z1#HO8FQA8VMW:61O=R]W;W)K87)E82]E;F%C=&UE;G0O
M8G5I;&0O8VQA<W-E<R]D:R]P:6YE+V5N86-T;65N="]S97)V:6-E<R]087)A
M;65T97)$968N:F1O#0I;<V-H96UA=&]O;%T@*&MO9&\N365T841A=&$@(" @
M(" @(" @(" @(" @(" @(" @(#@V(" I(&-O;2YS;VQA<FUE=')I8RYK;V1O
M+FUE=&$N2D1/365T841A=&%087)S97) ,C R9#8Y.B!P87)S:6YG('-O=7)C
M93H@9FEL93I$.B]B;&%C:W=I9&]W+W=O<FMA<F5A+V5N86-T;65N="]B=6EL
M9"]C;&%S<V5S+V1K+W!I;F4O96YA8W1M96YT+T%C=&EV:71Y+FID;PT*6W-C
M:&5M871O;VQ=("AK;V1O+DUE=&%$871A(" @(" @(" @(" @(" @(" @(" @
M(" X-B @*2!C;VTN<V]L87)M971R:6,N:V]D;RYM971A+DI$3TUE=&%$871A
M4&%R<V5R0#@U-34V,CH@<&%R<VEN9R!S;W5R8V4Z(&9I;&4Z1#HO8FQA8VMW
M:61O=R]W;W)K87)E82]E;F%C=&UE;G0O8G5I;&0O8VQA<W-E<R]D:R]P:6YE
M+V5N86-T;65N="]!8W1I=FET>4EN<W1A;F-E+FID;PT*6W-C:&5M871O;VQ=
M("AK;V1O+DUE=&%$871A(" @(" @(" @(" @(" @(" @(" @(" X-B @*2!C
M;VTN<V]L87)M971R:6,N:V]D;RYM971A+DI$3TUE=&%$871A4&%R<V5R0&$X
M.6-E,SH@<&%R<VEN9R!S;W5R8V4Z(&9I;&4Z1#HO8FQA8VMW:61O=R]W;W)K
M87)E82]E;F%C=&UE;G0O8G5I;&0O8VQA<W-E<R]D:R]P:6YE+V5N86-T;65N
M="].;V1E+FID;PT*6W-C:&5M871O;VQ=("AK;V1O+DUE=&%$871A(" @(" @
M(" @(" @(" @(" @(" @(" X-B @*2!C;VTN<V]L87)M971R:6,N:V]D;RYM
M971A+DI$3TUE=&%$871A4&%R<V5R0#)B-V1B,3H@<&%R<VEN9R!S;W5R8V4Z
M(&9I;&4Z1#HO8FQA8VMW:61O=R]W;W)K87)E82]E;F%C=&UE;G0O8G5I;&0O
M8VQA<W-E<R]D:R]P:6YE+V5N86-T;65N="]0<F]C97-S+FID;PT*6W-C:&5M
M871O;VQ=("AK;V1O+DUE=&%$871A(" @(" @(" @(" @(" @(" @(" @(" X
M-B @*2!C;VTN<V]L87)M971R:6,N:V]D;RYM971A+DI$3TUE=&%$871A4&%R
M<V5R0#0X9CAC.#H@<&%R<VEN9R!S;W5R8V4Z(&9I;&4Z1#HO8FQA8VMW:61O
M=R]W;W)K87)E82]E;F%C=&UE;G0O8G5I;&0O8VQA<W-E<R]D:R]P:6YE+V5N
M86-T;65N="]0<F]C97-S26YS=&%N8V4N:F1O#0I;<V-H96UA=&]O;%T@*&MO
M9&\N365T841A=&$@(" @(" @(" @(" @(" @(" @(" @(#@V(" I(&-O;2YS
M;VQA<FUE=')I8RYK;V1O+FUE=&$N2D1/365T841A=&%087)S97) 8S4T-C9B
M.B!P87)S:6YG('-O=7)C93H@9FEL93I$.B]B;&%C:W=I9&]W+W=O<FMA<F5A
M+V5N86-T;65N="]B=6EL9"]C;&%S<V5S+V1K+W!I;F4O96YA8W1M96YT+T5V
M96YT2&%N9&QE<BYJ9&\-"EMS8VAE;6%T;V]L72 H:V]D;RY-971A1&%T82 @
M(" @(" @(" @(" @(" @(" @(" @.#8@("D@8V]M+G-O;&%R;65T<FEC+FMO
M9&\N;65T82Y*1$]-971A1&%T85!A<G-E<D X,34S,S@Z('!A<G-I;F<@<V]U
M<F-E.B!F:6QE.D0Z+V)L86-K=VED;W<O=V]R:V%R96$O96YA8W1M96YT+V)U
M:6QD+V-L87-S97,O9&LO<&EN92]E;F%C=&UE;G0O1F%U;'1(86YD;&5R+FID
M;PT*6W-C:&5M871O;VQ=("AK;V1O+DUE=&%$871A(" @(" @(" @(" @(" @
M(" @(" @(" X-B @*2!C;VTN<V]L87)M971R:6,N:V]D;RYM971A+DI$3TUE
M=&%$871A4&%R<V5R0#=E.#0U83H@<&%R<VEN9R!S;W5R8V4Z(&9I;&4Z1#HO
M8FQA8VMW:61O=R]W;W)K87)E82]E;F%C=&UE;G0O8G5I;&0O8VQA<W-E<R]D
M:R]P:6YE+V5N86-T;65N="]-97-S86=E2&%N9&QE<BYJ9&\-"EMS8VAE;6%T
M;V]L72 H:V]D;RY-971A1&%T82 @(" @(" @(" @(" @(" @(" @(" @.#8@
M("D@8V]M+G-O;&%R;65T<FEC+FMO9&\N;65T82Y*1$]-971A1&%T85!A<G-E
M<D R,S8X9&8Z('!A<G-I;F<@<V]U<F-E.B!F:6QE.D0Z+V)L86-K=VED;W<O
M=V]R:V%R96$O96YA8W1M96YT+V)U:6QD+V-L87-S97,O9&LO<&EN92]E;F%C
M=&UE;G0O4V5R=FEC92YJ9&\-"EMS8VAE;6%T;V]L72 H:V]D;RY-971A1&%T
M82 @(" @(" @(" @(" @(" @(" @(" @.#8@("D@8V]M+G-O;&%R;65T<FEC
M+FMO9&\N;65T82Y*1$]-971A1&%T85!A<G-E<D!B83!F,S8Z('!A<G-I;F<@
M<V]U<F-E.B!F:6QE.D0Z+V)L86-K=VED;W<O=V]R:V%R96$O96YA8W1M96YT
M+V)U:6QD+V-L87-S97,O9&LO<&EN92]E;F%C=&UE;G0O06-T:6]N+FID;PT*
M6W-C:&5M871O;VQ=("AK;V1O+DUE=&%$871A(" @(" @(" @(" @(" @(" @
M(" @(" X-B @*2!C;VTN<V]L87)M971R:6,N:V]D;RYM971A+DI$3TUE=&%$
M871A4&%R<V5R0&0P,C(P8SH@<&%R<VEN9R!S;W5R8V4Z(&9I;&4Z1#HO8FQA
M8VMW:61O=R]W;W)K87)E82]E;F%C=&UE;G0O8G5I;&0O8VQA<W-E<R]D:R]P
M:6YE+V5N86-T;65N="]4:6UE;W5T2&%N9&QE<BYJ9&\-"EMS8VAE;6%T;V]L
M72 H:F1B8RY*1$)#(" @(" @(" @(" @(" @(" @(" @(" @(" @,S P("D@
M6R!#.C(S-C,V-S0[(%0Z-#(T-# Y-SL@1#HQ-#8P,#,W,2!=(&]P96XZ(&ID
M8F,Z<WEB87-E.E1D<SIS;F]W8F%L;#HU,# P+TU%1$E!/U-E<G9I8V5.86UE
M/4U%1$E!/U5315(]<V$F4$%34U=/4D0])DQ)5$5204Q?4$%204U3/71R=64@
M*'-A*0T*6W-C:&5M871O;VQ=("AJ9&)C+DI$0D,@(" @(" @(" @(" @(" @
M(" @(" @(" @(" S,# @*2!;($,Z,C,V,S8W-#L@5#HT,C0T,#DW.R!$.C$T
M-C P,S<Q(%T@8F5G:6X@<F]L;&)A8VL-"EMS8VAE;6%T;V]L72 H:F1B8RY*
M1$)#(" @(" @(" @(" @(" @(" @(" @(" @(" @,S P("D@6R!#.C(S-C,V
M-S0[(%0Z-#(T-# Y-SL@1#HQ-#8P,#,W,2!=(&5N9"!R;VQL8F%C:R Q,&US
M#0I;<V-H96UA=&]O;%T@*&ID8F,N2D1"0R @(" @(" @(" @(" @(" @(" @
M(" @(" @(#,P," I(%L@0SHR,S8S-C<T.R!4.C0R-#0P.3<[($0Z,30V,# S
M-S$@72!R971U<FX@6V-O;2YS;VQA<FUE=')I8RYD871A<V]U<F-E+E!O;VQ#
M;VYN96-T:6]N0#(T,3$Q85M;<F5Q=65S=',],#MS:7IE/3 [;6%X/3<P.VAI
M=',],#MC<F5A=&5D/3 [<F5D=6YD86YT/3 [;W9E<F9L;W<],#MN97<],#ML
M96%K960],#MU;F%V86EL86)L93TP75U=('1O(%MC;VTN<V]L87)M971R:6,N
M9&%T87-O=7)C92Y$871A4V]U<F-E26UP;"13;W)T86)L95!O;VQ;;6EN/3 [
M(&UA>#TQ,#L@875T;W)E='5R;CTQ,#L@<VEZ93TP.R!T86ME;CTP75T-"EMS
M8VAE;6%T;V]L72 H:F1B8RY*1$)#(" @(" @(" @(" @(" @(" @(" @(" @
M(" @,S0X("D@57-I;F<@9&EC=&EO;F%R>2!C;&%S<R B8V]M+G-O;&%R;65T
M<FEC+FMO9&\N:6UP;"YJ9&)C+G-C:&5M82YD:6-T+E-Y8F%S941I8W1I;VYA
M<GDB('1O(&-O;FYE8W0@=&\@(D%D87!T:79E(%-E<G9E<B!%;G1E<G!R:7-E
M(B H=F5R<VEO;B B061A<'1I=F4@4V5R=F5R($5N=&5R<')I<V4O,3(N-2XP
M+C$O14)&(#$P-#,P($531",R+U O3E0@*$E8.#8I+T]3(#0N,"]R96PQ,C4P
M,2\Q+S,R+6)I="]/4%0O5'5E($IU;" S," R,SHT-3HU-R R,# R(BD@=VET
M:"!*1$)#(&1R:79E<B B:D-O;FYE8W0@*%1-*2!F;W(@2D1"0R H5$TI(B H
M=F5R<VEO;B B:D-O;FYE8W0@*%1-*2!F;W(@2D1"0RA432DO-"XR*$)U:6QD
M(#$R-C<I+U O14)&.3DY.2]*1$LQ,2]&<FD@1&5C(#$T(#$Q.C(U.C(P(#(P
M,#$B*0T*6W-C:&5M871O;VQ=("AJ9&)C+E-C:&5M82 @(" @(" @(" @(" @
M(" @(" @(" @(" Y-S(@*2!2969R97-H:6YG('-C:&5M82!F;W(@='EP92 B
M8VQA<W,@9&LN<&EN92YE;F%C=&UE;G0N4')O8V5S<R(@86YD(&%L;"!K;F]W
M;B!S=6)C;&%S<V5S#0I;<V-H96UA=&]O;%T@*&ID8F,N2D1"0R @(" @(" @
M(" @(" @(" @(" @(" @(" @(#DY-2 I(&IA=F$N<W%L+E-13%=A<FYI;F<Z
M(&IA=F$N<W%L+E-13%=A<FYI;F<Z(# Q,$U8.B!-971A9&%T82!A8V-E<W-O
M<B!I;F9O<FUA=&EO;B!W87,@;F]T(&9O=6YD(&]N('1H:7,@9&%T86)A<V4N
M(%!L96%S92!I;G-T86QL('1H92!R97%U:7)E9"!T86)L97,@87,@;65N=&EO
M;F5D(&EN('1H92!J0V]N;F5C="!D;V-U;65N=&%T:6]N+B!%<G)O<B!E;F-O
M=6YT97)E9"!W:&EL92!A='1E;7!T:6YG('1O(')E=')I979E(&UE=&%D871A
M(&EN9F]R;6%T:6]N.B!C;VTN<WEB87-E+FID8F,N4WEB4U%,17AC97!T:6]N
M.B!);F-O<G)E8W0@<WEN=&%X(&YE87(@)TU%1$E!)RX-"EMS8VAE;6%T;V]L
M72 H:F1B8RY*1$)#(" @(" @(" @(" @(" @(" @(" @(" @(" @.3DU("D@
M:F%V82YS<6PN4U%,5V%R;FEN9SH@:F%V82YS<6PN4U%,5V%R;FEN9SH@,#$P
M1% Z($1U<&QI8V%T92!C;VYN96-T:6]N('!R;W!E<G1Y(%!!4U-73U)$(&EG
M;F]R960N#0I;<V-H96UA=&]O;%T@*&ID8F,N4V-H96UA(" @(" @(" @(" @
M(" @(" @(" @(" @(#DW,B I($-214%412!404),12!04D]#15-36" H1$53
M0U)8(%9!4D-(05(H,C4U*2!.54Q,+"!*1$]#3$%34U@@5D%20TA!4B@R-34I
M($Y53$PL($I$3TE$6"!.54U%4DE#($Y/5"!.54Q,+"!*1$],3T-+6"!)3E1%
M1T52($Y53$PL($Y!3458(%9!4D-(05(H,C4U*2!.54Q,+"!04DE-05)9($M%
M62 H2D1/2418*2D-"EMS8VAE;6%T;V]L72 H:F1B8RY344P@(" @(" @(" @
M(" @(" @(" @(" @(" @(" @,S P("D@6R!#.C(S-C,V-S0[(%0Z-#(T-# Y
M-SL@1#HQ-#8P,#,W,2!=($-214%412!404),12!04D]#15-36" H1$530U)8
M(%9!4D-(05(H,C4U*2!.54Q,+"!*1$]#3$%34U@@5D%20TA!4B@R-34I($Y5
M3$PL($I$3TE$6"!.54U%4DE#($Y/5"!.54Q,+"!*1$],3T-+6"!)3E1%1T52
M($Y53$PL($Y!3458(%9!4D-(05(H,C4U*2!.54Q,+"!04DE-05)9($M%62 H
M2D1/2418*2D-"EMS8VAE;6%T;V]L72 H:F1B8RY38VAE;6$@(" @(" @(" @
M(" @(" @(" @(" @(" @.3<R("D@0U)%051%(%1!0DQ%(%!23T-%4U-8("A$
M15-#4E@@5D%20TA!4B@R-34I($Y53$PL($I$3T-,05-36"!605)#2$%2*#(U
M-2D@3E5,3"P@2D1/2418($Y5345224,@3D]4($Y53$PL($I$3TQ/0TM8($E.
M5$5'15(@3E5,3"P@3D%-15@@5D%20TA!4B@R-34I($Y53$PL(%!224U!4ED@
M2T59("A*1$])1%@I*0T*6W-C:&5M871O;VQ=("AJ9&)C+DI$0D,@(" @(" @
M(" @(" @(" @(" @(" @(" @(" S,# @*2!;($,Z,C,V,S8W-#L@5#HT,C0T
M,#DW.R!$.C$T-C P,S<Q(%T@8VQO<V4@*#$@97)R;W)S*3H@8V]M+G-O;&%R
M;65T<FEC+F1A=&%S;W5R8V4N4&]O;$-O;FYE8W1I;VY ,C0Q,3%A6UMR97%U
M97-T<STP.W-I>F4],#MM87@]-S [:&ET<STP.V-R96%T960],#MR961U;F1A
M;G0],#MO=F5R9FQO=STP.VYE=STP.VQE86ME9#TP.W5N879A:6QA8FQE/3!=
M70T*6W-C:&5M871O;VQ=("AJ9&)C+DI$0D,@(" @(" @(" @(" @(" @(" @
M(" @(" @(" S,# @*2!;($,Z,C,V,S8W-#L@5#HT,C0T,#DW.R!$.C$T-C P
M,S<Q(%T@8VQO<V4@8V]N;F5C=&EO;@T*6W-C:&5M871O;VQ=(&-O;2YS>6)A
M<V4N:F1B8RY3>6)344Q%>&-E<'1I;VXZ(%1H92 G0U)%051%(%1!0DQ%)R!C
M;VUM86YD(&ES(&YO="!A;&QO=V5D('=I=&AI;B!A(&UU;'1I+7-T871E;65N
M="!T<F%N<V%C=&EO;B!I;B!T:&4@)TU%1$E!)R!D871A8F%S92X-"@T*6W-C
M:&5M871O;VQ=(" @(&%T(&-O;2YS>6)A<V4N=&1S+E1D<RYP<F]C97-S165D
M*%1D<RYJ879A*0T*6W-C:&5M871O;VQ=(" @(&%T(&-O;2YS>6)A<V4N=&1S
M+E1D<RYN97AT4F5S=6QT*%1D<RYJ879A*0T*6W-C:&5M871O;VQ=(" @(&%T
M(&-O;2YS>6)A<V4N:F1B8RY297-U;'1'971T97(N;F5X=%)E<W5L="A297-U
M;'1'971T97(N:F%V82D-"EMS8VAE;6%T;V]L72 @("!A="!C;VTN<WEB87-E
M+FID8F,N4WEB4W1A=&5M96YT+FYE>'1297-U;'0H4WEB4W1A=&5M96YT+FIA
M=F$I#0I;<V-H96UA=&]O;%T@(" @870@8V]M+G-Y8F%S92YJ9&)C+E-Y8E-T
M871E;65N="YU<&1A=&5,;V]P*%-Y8E-T871E;65N="YJ879A*0T*6W-C:&5M
M871O;VQ=(" @(&%T(&-O;2YS>6)A<V4N:F1B8RY3>6)3=&%T96UE;G0N97AE
M8W5T955P9&%T92A3>6)3=&%T96UE;G0N:F%V82D-"EMS8VAE;6%T;V]L72 @
M("!A="!C;VTN<WEB87-E+FID8F,N4WEB4W1A=&5M96YT+F5X96-U=&55<&1A
M=&4H4WEB4W1A=&5M96YT+FIA=F$I#0I;<V-H96UA=&]O;%T@(" @870@8V]M
M+G-O;&%R;65T<FEC+F1A=&%S;W5R8V4N4&]O;$-O;FYE8W1I;VXD4&]O;%-T
M871E;65N="YE>&5C=71E57!D871E*%!O;VQ#;VYN96-T:6]N+FIA=F$Z,3$R
M*0T*6W-C:&5M871O;VQ=(" @(&%T(&-O;2YS;VQA<FUE=')I8RYK;V1O+FEM
M<&PN:F1B8RYS8VAE;6$N4V-H96UA5&]O;"YE>&5C=71E4U%,*%-C:&5M851O
M;VPN:F%V83HX.3DI#0I;<V-H96UA=&]O;%T@(" @870@8V]M+G-O;&%R;65T
M<FEC+FMO9&\N:6UP;"YJ9&)C+G-C:&5M82Y38VAE;6%4;V]L+F-R96%T951A
M8FQE*%-C:&5M851O;VPN:F%V83HX,S I#0I;<V-H96UA=&]O;%T@(" @870@
M8V]M+G-O;&%R;65T<FEC+FMO9&\N:6UP;"YJ9&)C+G-C:&5M82Y38VAE;6%4
M;V]L+F%D9%1A8FQE*%-C:&5M851O;VPN:F%V83HT,S<I#0I;<V-H96UA=&]O
M;%T@(" @870@8V]M+G-O;&%R;65T<FEC+FMO9&\N:6UP;"YJ9&)C+G-C:&5M
M82Y38VAE;6%4;V]L+F%D9%1A8FQE<RA38VAE;6%4;V]L+FIA=F$Z-#0X*0T*
M6W-C:&5M871O;VQ=(" @(&%T(&-O;2YS;VQA<FUE=')I8RYK;V1O+FEM<&PN
M:F1B8RYS8VAE;6$N4V-H96UA5&]O;"YR969R97-H*%-C:&5M851O;VPN:F%V
M83HS-C,I#0I;<V-H96UA=&]O;%T@(" @870@8V]M+G-O;&%R;65T<FEC+FMO
M9&\N:6UP;"YJ9&)C+G-C:&5M82Y38VAE;6%4;V]L+G)E9G)E<V@H4V-H96UA
M5&]O;"YJ879A.C,R,2D-"EMS8VAE;6%T;V]L72 @("!A="!C;VTN<V]L87)M
M971R:6,N:V]D;RYI;7!L+FID8F,N<V-H96UA+E-C:&5M851O;VPN;6%I;BA3
M8VAE;6%4;V]L+FIA=F$Z,3$S,BD-"EMS8VAE;6%T;V]L72 @("!A="!C;VTN
M<V]L87)M971R:6,N:V]D;RYI;7!L+FID8F,N<V-H96UA+E-C:&5M851O;VPN
M;6%I;BA38VAE;6%4;V]L+FIA=F$Z,3 V.2D-"EMS8VAE;6%T;V]L72 @("!A
M="!C;VTN<V]L87)M971R:6,N;6]D=6QE<RYI;G1E9W)A=&EO;BYA;G0N4V-H
M96UA5&]O;%1A<VLN97AE8W5T94]N*%-C:&5M851O;VQ487-K+FIA=F$Z-30I
M#0I;<V-H96UA=&]O;%T@(" @870@8V]M+G-O;&%R;65T<FEC+FUO9'5L97,N
M:6YT96=R871I;VXN86YT+E1A<VM"87-E+F5X96-U=&4H5&%S:T)A<V4N:F%V
M83HQ,3@I#0I;<V-H96UA=&]O;%T@(" @870@;W)G+F%P86-H92YT;V]L<RYA
M;G0N56YK;F]W;D5L96UE;G0N97AE8W5T92A5;FMN;W=N16QE;65N="YJ879A
M.C$V-BD-"EMS8VAE;6%T;V]L72 @("!A="!O<F<N87!A8VAE+G1O;VQS+F%N
M="Y487-K+G!E<F9O<FTH5&%S:RYJ879A.C,Q-RD-"EMS8VAE;6%T;V]L72 @
M("!A="!O<F<N87!A8VAE+G1O;VQS+F%N="Y487)G970N97AE8W5T92A487)G
M970N:F%V83HS,#DI#0I;<V-H96UA=&]O;%T@(" @870@;W)G+F%P86-H92YT
M;V]L<RYA;G0N5&%R9V5T+G!E<F9O<FU487-K<RA487)G970N:F%V83HS,S0I
M#0I;<V-H96UA=&]O;%T@(" @870@;W)G+F%P86-H92YT;V]L<RYA;G0N4')O
M:F5C="YE>&5C=71E5&%R9V5T*%!R;VIE8W0N:F%V83HQ,S V*0T*6W-C:&5M
M871O;VQ=(" @(&%T(&]R9RYA<&%C:&4N=&]O;',N86YT+E!R;VIE8W0N97AE
M8W5T951A<F=E=',H4')O:F5C="YJ879A.C$R-3 I#0I;<V-H96UA=&]O;%T@
M(" @870@;W)G+F%P86-H92YT;V]L<RYA;G0N36%I;BYR=6Y"=6EL9"A-86EN
M+FIA=F$Z-C$P*0T*6W-C:&5M871O;VQ=(" @(&%T(&]R9RYA<&%C:&4N=&]O
M;',N86YT+DUA:6XN<W1A<G0H36%I;BYJ879A.C$Y-BD-"EMS8VAE;6%T;V]L
M72 @("!A="!O<F<N87!A8VAE+G1O;VQS+F%N="Y-86EN+FUA:6XH36%I;BYJ
*879A.C(S-2D-"@``
`
end

This is a bug in our 2.4.0 release. It has been resolved internally, and
a fix will be available in 2.4.1.
In the mean time, use the -outfile option to schematool to output a DDL,
and manually run this DDL against your schema.
-Patrick
On Wed, 22 Jan 2003 05:22:56 -0500, Jesper Ladegaard wrote:
Running the schematool or using the SynchronizeSchema feature, I get the
following exception on sybase:
com.sybase.jdbc.SybSQLException: The 'CREATE TABLE' command is not
allowed within a multi-statement transaction in the 'MEDIA' database.
The same application deploys fine using SQL-server or Oracle.
I'm using kodo 2.4.0.
Any ideas?
Detailed exception included in attachment.
Regards
Jesper--
Patrick Linskey
SolarMetric Inc.

Problem capturing source model sybase apative server 11.5.1

Trying to migrate production Sybase Adaptive Server database to
Oracle using Oracle Migratin Workbench-Sybase Plugin. It fails
duing loading source model stage. Sybase database is not going
to be available to us for long as companies are separating by
december end, four databases need to be migrated by then. It is
very important to get the migratin done and there is no
workaround this problem. This is showstopper for migration
project right now.
Details:
Oracle Migration Workbench with sybase adaptive server 11 plugin
     2.0.2.0.0     Production Build 20011121 Windows-
2000professional
Oracle Database               8.1.7          Solaris 8
Sybase Database               Sybase Adaptive Server 11.5.1
     Solaris 8
Source ODBC Driver          3.11.00.01 Windows-
2000Professional
Stage of migration: Loading Source Database
Error Text on alert window:
Failed to load Source Model. [INTERSOLV][ODBC SQL Server driver]
[SQL Server]Invalid column name 'fill_factor'
Error Text in the log file:
EXCEPTION : LoadTableData.run() : SYBASE11_SYSINDEXES [INTERSOLV]
[ODBC SQL Server driver][SQL Server]Invalid column
name 'fill_factor'.
After Investingation it looks like the table sybase11_sysindexes
in OMWB repository has four columns extra than the sysindexes
table in sybase database. The additional four columns are:
fill_factor, res_page_gap, exp_rowsize, key3. OMWB load source
model step fails on the first column.
Trying to load the sybase source model using Oracle Migration
Workbench.
Oracle Migration workbench was running.
Oracle Migratin workbench capture wizard was running.
Installed OMWB and sybase apative server 11 plugin for OMWB.
Installed Sybase client for windows and ODBC drivers.
Configured ODBC for sybase database as a system DSN.
Created empty scheama with connect and resource privilages for
OMWB repository on Oracle 8.1.7 on solaris 8.
Started OMWB, created repository in the empty scheama created
above.
Clicked on capture source database wizard.
Provided the userid, password and database for sybase database.
Selected not to generate Oracle model, as it can be generated
afterwards.
Clicked finish on the wizard.
OMWB started reading sybase system repository tables, it did a
few tables and then the above error message appeared.
This is a fresh install of Windows 2000 Professional.
The only oracle product installed in OMWB and the Sybase
Apadative server 11 Plugin for OMWB.
The other software is Sybase client for windows (To do queries
on Sybase database) and the sybase ODBC driver.
No other significant software is installed, it a vanila windows
2000 Professional installation.
There is oracle tar for this. TAR 1828907.995
Any help is appriciated.
Thanks,
Prashant

Hi,
Without seeing the full error.log file here are some suggestions.
>
From Prashant's e-mail it appears that the data dictionary's of11.5.1.
and 11.9.2 are different.
A possible alternative that may help i.e. removing the 4 extracolumns
that Prashant talks about from the Workbench source model e.g.
Sybase11_sysindexes. This may help you get around this issue
If that does not work. One possible workaround is as follows.
Extract the Schema generation scripts from the Sybase 11.5.1database
and re-create the schema in Sybase 11.9.2. You don't have tomove the data.
>
You can then migrate the schema from the Sybase 11.9.2database. Once
the schema is migrated you can generate the SQL Loader scripts to
migrate the data. Click on the Tools menu and then select the'Generate
SQL Loader Scripts...' menu item. This will generate Sybase BCPdata
extraction scripts. These scripts will extract the Sybase datafrom each
table into a separate .dat file. You can then use the SQL Loaeder
scripts that were also generated to load this data in to thedestination
Oracle database.
Regards
John

Problem with capturing of baselines

Hi !
I have a problem with capturing of baselines- when the SQL is called from PL/SQL code...
For example if I execute in SQL* Plus session
alter session set optimizer_capture_sql_plan_baselines = true;
exec dbms_mview.refresh('VIEW_CLIENT_KONTO', 'C');
exec dbms_mview.refresh('VIEW_CLIENT_KONTO', 'C');
nothing happens ..I do not find the baseline in dba_sql_plan_baselines...
========================================================
optimizer_use_sql_plan_baselines = TRUE..of course and I can capture baselines for plain SQL -only not if SQL ist invoked from PL/SQL..
Now, nowere in documentation could I find that capturing does not work from PL/SQL ..that would, in my opinion, be sderious disadvantage- so much code in the database runs as PL/SQL..
We habe Oracle 11.2.0.3 Enterprise Edition
optimizer_features_enable = 11.2.0.3
What could be worng here..did I forget certain parameter or setting. Thanks for your help in advance.

Now, nowere in documentation could I find that capturing does not work from PL/SQL ..that would, in my opinion,
be sderious disadvantage- so much code in the database runs as PL/SQL..You're quite right. It would be serious disadvantage.
But it's not true that they are not captured from PLSQL.
Setup:
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE    11.2.0.3.0      Production
TNS for Linux: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
SQL> select name, value from v$parameter where name like '%baseline%';
NAME                                               VALUE
optimizer_capture_sql_plan_baselines               FALSE
optimizer_use_sql_plan_baselines                   TRUE
SQL> create table t1
2 (col1 number);
Table created.
SQL> INSERT /*+ domtest sql */ INTO t1 select 1 from dual;
1 row created.
SQL> begin
2 INSERT /*+ domtest plsql */ INTO t1 select 1 from dual;
3 end;
4 /
PL/SQL procedure successfully completed.
SQL> select sql_id, substr(sql_text,1,30) sql_text, child_number c, to_char(force_matching_signature
) sig, sql_plan_baseline
2 from   v$sql
3 where sql_text like 'INSERT /*+ domtest%';
SQL_ID        SQL_TEXT                                C SIG                            SQL_PLAN_BASELINE
gmskus7sbgt5d INSERT /*+ domtest plsql */ IN          0 7407988653257810022
64rzqgrt63wzu INSERT /*+ domtest sql */ INTO          0 17374141102446297863
SQL> select to_char(b.signature) sig, b.created
2 from   v$sql s
3 ,      dba_sql_plan_baselines b
4 where s.sql_text like 'INSERT /*+ domtest%'
5 and    b.signature = s.force_matching_signature;
no rows selected
SQL> alter session set optimizer_capture_sql_plan_baselines = true;
Session altered.
SQL> Baseline created for SQL statement:
SQL> INSERT /*+ domtest sql */ INTO t1 select 1 from dual;
1 row created.
SQL> select sql_id
2 ,      substr(sql_text,1,30) sql_text
3 ,      child_number c
4 ,      to_char(force_matching_signature) sig
5 ,      sql_plan_baseline
6 from   v$sql
7 where sql_text like 'INSERT /*+ domtest%';
SQL_ID        SQL_TEXT                                C SIG                            SQL_PLAN_BASELINE
gmskus7sbgt5d INSERT /*+ domtest plsql */ IN          0 7407988653257810022
64rzqgrt63wzu INSERT /*+ domtest sql */ INTO          0 17374141102446297863
64rzqgrt63wzu INSERT /*+ domtest sql */ INTO          1 17374141102446297863           SQL_PLAN_1ayk9a0wnr
SQL> Baseline created for PLSQL statement:
SQL> begin
2 INSERT /*+ domtest plsql */ INTO t1 select 1 from dual;
3 end;
4 /
PL/SQL procedure successfully completed.
SQL> select sql_id
2 ,      substr(sql_text,1,30) sql_text
3 ,      child_number c
4 ,      to_char(force_matching_signature) sig
5 ,      sql_plan_baseline
6 from   v$sql
7 where sql_text like 'INSERT /*+ domtest%';
SQL_ID        SQL_TEXT                                C SIG                            SQL_PLAN_BASELINE
gmskus7sbgt5d INSERT /*+ domtest plsql */ IN          0 7407988653257810022
gmskus7sbgt5d INSERT /*+ domtest plsql */ IN          1 7407988653257810022            SQL_PLAN_5s3v02k7yx9
64rzqgrt63wzu INSERT /*+ domtest sql */ INTO          0 17374141102446297863
64rzqgrt63wzu INSERT /*+ domtest sql */ INTO          1 17374141102446297863           SQL_PLAN_1ayk9a0wnr
SQL> Cleanup baselines:
SQL> declare
2   l_spm_op pls_integer;
3 begin
4   for x in (select sql_handle from dba_sql_plan_baselines b where created >= trunc(sysdate))
5   loop
6       l_spm_op :=
7       dbms_spm.drop_sql_plan_baseline(x.sql_handle);
8   end loop;
9 end;
10 /
PL/SQL procedure successfully completed.
SQL> So, I would expect that this is related to DBMS_MVIEW and a restriction on recursive, internal statements.
For example, if you capture sql plan baselines you don't capture baselines for sys and system statements, etc.
Further investigation required.
For example, let's build an MV:
SQL> create materialized view mv1
2 build immediate
3 refresh on demand
4 as
5 select /*+ domtest mv */ col1 from t1;
Materialized view created.
SQL> exec dbms_mview.refresh('MV1');
PL/SQL procedure successfully completed.
SQL> We see two statements from the initial creation of the MV and the subsequent refresh (the latter is the one with the BYPASS_RECURSIVE_CHECK hint).
SQL> select sql_id
2 ,      substr(sql_text,1,50) sql_text
3 ,      child_number c
4 ,      to_char(force_matching_signature) sig
5 ,      sql_plan_baseline
6 from   v$sql
7 where sql_text like 'INSERT %domtest%';
SQL_ID        SQL_TEXT                                C SIG                            SQL_PLAN_BASELINE
ctyufr5b5yzfm INSERT INTO "RIMS"."MV1" selec          0 12798978218302414227
              t /*+ domtest mv */
gfa550uufmr34 INSERT /*+ BYPASS_RECURSIVE_CH          0 12927173360082366872
              ECK */ INTO "RIMS"."
SQL> Even if we repeat the refresh, we can't see to get a baseline:
SQL> exec dbms_mview.refresh('MV1');
PL/SQL procedure successfully completed.
SQL> exec dbms_mview.refresh('MV1');
PL/SQL procedure successfully completed.
SQL> exec dbms_mview.refresh('MV1');
PL/SQL procedure successfully completed.
SQL> exec dbms_mview.refresh('MV1');
PL/SQL procedure successfully completed.
SQL> exec dbms_mview.refresh('MV1');
PL/SQL procedure successfully completed.
SQL> exec dbms_mview.refresh('MV1');
PL/SQL procedure successfully completed.
SQL> select sql_id
2 ,      substr(sql_text,1,50) sql_text
3 ,      child_number c
4 ,      to_char(force_matching_signature) sig
5 ,      sql_plan_baseline
6 from   v$sql
7 where sql_text like 'INSERT %domtest%';
SQL_ID        SQL_TEXT                                C SIG                            SQL_PLAN_BASELINE
ctyufr5b5yzfm INSERT INTO "RIMS"."MV1" selec          0 12798978218302414227
              t /*+ domtest mv */
gfa550uufmr34 INSERT /*+ BYPASS_RECURSIVE_CH          0 12927173360082366872
              ECK */ INTO "RIMS"."
SQL> So.... might that BYPASS_RECURSIVE_CHECK have anything to do with it?
It's not likely to be relevant but perhaps we should just check it?
Let's see what happens if we go back to our original plsql statement because we can't insert into an MV directly.
SQL> begin
2   INSERT /*+ BYPASS_RECURSIVE_CHECK */ INTO t1 select 1 from dual;
3 end;
4 /
PL/SQL procedure successfully completed.
SQL> select sql_id
2 ,      substr(sql_text,1,50) sql_text
3 ,      child_number c
4 --,      to_char(force_matching_signature) sig
5 ,      sql_plan_baseline
6 from   v$sql
7 where sql_text like 'INSERT /*+ BYPASS_RECURSIVE_CHECK */%';
SQL_ID        SQL_TEXT                                                    C SQL_PLAN_BASELINE
6kjvr1gu6v2pq INSERT /*+ BYPASS_RECURSIVE_CHECK */ INTO T1 SELEC          0
SQL> begin
2   INSERT /*+ BYPASS_RECURSIVE_CHECK */ INTO t1 select 1 from dual;
3 end;
4 /
PL/SQL procedure successfully completed.
SQL> select sql_id
2 ,      substr(sql_text,1,50) sql_text
3 ,      child_number c
4 --,      to_char(force_matching_signature) sig
5 ,      sql_plan_baseline
6 from   v$sql
7 where sql_text like 'INSERT /*+ BYPASS_RECURSIVE_CHECK */%';
SQL_ID        SQL_TEXT                                                    C SQL_PLAN_BASELINE
6kjvr1gu6v2pq INSERT /*+ BYPASS_RECURSIVE_CHECK */ INTO T1 SELEC          0
SQL> begin
2   INSERT /*+ BYPASS_RECURSIVE_CHECK */ INTO t1 select 1 from dual;
3 end;
4 /
PL/SQL procedure successfully completed.
SQL> select sql_id
2 ,      substr(sql_text,1,50) sql_text
3 ,      child_number c
4 --,      to_char(force_matching_signature) sig
5 ,      sql_plan_baseline
6 from   v$sql
7 where sql_text like 'INSERT /*+ BYPASS_RECURSIVE_CHECK */%';
SQL_ID        SQL_TEXT                                                    C SQL_PLAN_BASELINE
6kjvr1gu6v2pq INSERT /*+ BYPASS_RECURSIVE_CHECK */ INTO T1 SELEC          0
6kjvr1gu6v2pq INSERT /*+ BYPASS_RECURSIVE_CHECK */ INTO T1 SELEC          1 SQL_PLAN_aq62u7rqdfcs8125daea2
SQL> So, nothing to do with that.
I would suggest that it is because, being executed via DBMS_MVIEW, it is special and bypasses consideration for baselines.
Can we somehow circumvent this?
Perhaps, baselines being a pretty flexible vehicle that work off SIGNATURE (and PLAN_HASH_2).
Let's double check the signature and plan hash we need to reproduce.
SQL> select sql_id
2 ,      substr(sql_text,1,50) sql_text
3 ,      child_number c
4 ,      to_char(force_matching_signature) sig
5 ,      sql_plan_baseline
6 ,      plan_hash_value
7 from   v$sql
8 where sql_text like 'INSERT %domtest%';
SQL_ID        SQL_TEXT                                C SIG                            SQL_PLAN_BASELINE
PLAN_HASH_VALUE
ctyufr5b5yzfm INSERT INTO "RIMS"."MV1" selec          0 12798978218302414227
              t /*+ domtest mv */
     3617692013
gfa550uufmr34 INSERT /*+ BYPASS_RECURSIVE_CH          0 12927173360082366872
              ECK */ INTO "RIMS"."
     3617692013
SQL> And replace the materialized view with a table:
SQL> drop materialized view mv1;
Materialized view dropped.
SQL> create table mv1
2 (col1 number);
Table created.
SQL> And try to get a statement with the same signature and plan that does use a baseline:
SQL> begin
2   INSERT /*+ BYPASS_RECURSIVE_CHECK */ INTO "RIMS"."MV1" select /*+ domtest mv */ col1 from t1 ;
3 end;
4 /
PL/SQL procedure successfully completed.
SQL> select sql_id
2 ,      substr(sql_text,1,50) sql_text
3 ,      child_number c
4 ,      to_char(force_matching_signature) sig
5 ,      sql_plan_baseline
6 ,      plan_hash_value
7 from   v$sql
8 where sql_text like 'INSERT %domtest%';
SQL_ID        SQL_TEXT                                C SIG                            SQL_PLAN_BASELINE
PLAN_HASH_VALUE
ctyufr5b5yzfm INSERT INTO "RIMS"."MV1" selec          0 12798978218302414227
              t /*+ domtest mv */
     3617692013
5n6auhnqpb258 INSERT /*+ BYPASS_RECURSIVE_CH          0 12927173360082366872           SQL_PLAN_b6tnbps6tn
              ECK */ INTO "RIMS".
     3617692013
gfa550uufmr34 INSERT /*+ BYPASS_RECURSIVE_CH          0 12927173360082366872
              ECK */ INTO "RIMS"."
     3617692013
SQL> Now if we drop and recreate the materialized view:
SQL> create materialized view mv1
2 build immediate
3 refresh on demand
4 as
5 select /*+ domtest mv */ col1 from t1;
Materialized view created.
SQL> exec dbms_mview.refresh('MV1');
PL/SQL procedure successfully completed.
SQL> select sql_id
2 ,      substr(sql_text,1,50) sql_text
3 ,      child_number c
4 ,      to_char(force_matching_signature) sig
5 ,      sql_plan_baseline
6 ,      plan_hash_value
7 from   v$sql
8 where sql_text like 'INSERT %domtest%';
SQL_ID        SQL_TEXT                                C SIG                            SQL_PLAN_BASELINE
PLAN_HASH_VALUE
dac4d22mf0m6k INSERT INTO "RIMS"."MV1" selec          0 12798978218302414227
              t /*+ domtest mv */
     3617692013
cn4syqz9cxp3y INSERT /*+ BYPASS_RECURSIVE_CH          0 12927173360082366872           SQL_PLAN_b6tnbps6tn
              ECK */ INTO "RIMS"."
     3617692013
SQL> And cleanup:
SQL> drop table t1;
Table dropped.
SQL> drop materialized view mv1;
Materialized view dropped.
SQL> declare
2   l_spm_op pls_integer;
3 begin
4   for x in (select sql_handle from dba_sql_plan_baselines b where created >= trunc(sysdate))
5   loop
6       l_spm_op :=
7       dbms_spm.drop_sql_plan_baseline(x.sql_handle);
8   end loop;
9 end;
10 /
PL/SQL procedure successfully completed.
SQL> So....
Are baselines created for sql statements executed from PLSQL? Yes.
Are baselines created for internal statements from DBMS_MVIEW? No.
Why? Don't know. But I think it's expected behaviour.
Is there a convoluted way of applying a baseline to the internal refresh statement? Yes.

Problem converting captured SQL Server 2000 database to Oracle

Java(TM) Platform     1.6.0_17
Oracle IDE     2.1.1.64.45
Versioning Support     2.1.1.64.45
After creating MWREP user, granting it privileges and creating the migration repository, I have captured a small SQL Server 2000 database (1 table), but after performing "Convert to Oracle", I get the message that it has transformed correctly, but no converted model is shown. I was originally using the JRE supplied with SQL Developer 2.1.1, but replaced that with 1.6 U17 after researching the problem here.
The only message in the Migration Log is as follows:
Catalog RAC, Schema dbo coalesced to single schema dbo_RAC
The following message appears in the console:
SELECT DISTINCT(REF_ID_FK), REF_TYPE FROM MD_ADDITIONAL_PROPERTIES WHERE PROP_KEY IN (?) AND CONNECTION_ID_FK = ?
I have tried this with a more complex database, with no luck.
Any thoughts?

I did an offline capture.
I used Tools->Migration->Third Party Database Offline Capture->Create Database Capture Scripts to generate scripts OMWB_OFFLINE_CAPTURE.BAT, SS2K_BCP_SCRIPT.BAT and sqlserver2000.ocp. Then the SQL Server DBA ran OMWB_OFFLINE_CAPTURE.BAT and sent me the output.
I used Tools->Migration->Third Party Database Offline Capture->Load Database Capture Scripts Output to capture the model into the repository successfully.

Problem in capturing Tableview Selectedrow contents

Hi I am experiencing problem in capturing the contents of the selected row in the tableview. My Code looks like as follows:
Layout
<%@page language="abap" %>
<%@extension name="htmlb" prefix="htmlb" %>
<htmlb:content design="design2003" >
<%-- <%@include file="head.htm" %> --%>
<htmlb:page title="Company Code Search " >
 <htmlb:form>
 <htmlb:label for = "l_CCODE"
 text = "Field"
 tooltip = "User ID"
 required = "X"
 width = "100px"
 design = "EMPHASIZED" />
 <htmlb:dropdownListBox id = "ddname">
 <htmlb:listBoxItem key = "li_bukrs"
 value = "Company Code" />
 <htmlb:listBoxItem key = "li_butxt"
 value = "Company Code Description" />
 </htmlb:dropdownListBox>
 <htmlb:inputField id = "i_search"
 value = "Search term" />
 <htmlb:button id = "b_search"
 text = "Search"
 tooltip = "click here to start the search"
 onClick = "onInputProcessing(select)" />
 
 <htmlb:tableView id = "tv_tabid"
 table = "<%= gt_t001 %>"
 design = "STANDARD"
 designMode = "HTMLB"
 allRowsEditable = "TRUE"
 tableLayout = "AUTO"
 width = "75%"
 visibleFirstRow = "1"
 visibleRowCount = "10"
 headerVisible = "TRUE"
 headerText = "Company Code Selection Table"
 onRowSelection = "onInputProcessing(select)"
 selectionMode = "SINGLESELECT"
 selectedRowKey = "wa-BUKRS"
 navigationMode = "BYPAGE"
 footerVisible = "TRUE" >
 <htmlb:tableViewColumn columnName="BUKRS"
 title= "Company Code">
 </htmlb:tableViewColumn>
 <htmlb:tableViewColumn columnName="BUTXT"
 title= "Description">
 </htmlb:tableViewColumn>
 </htmlb:tableView>
 </htmlb:form>
</htmlb:page>
</htmlb:content>
OnInputProcessing
event = cl_htmlb_manager=>get_event( request ).
CASE event->id.
WHEN 'b_search'.
 DATA: l_ccode TYPE REF TO cl_htmlb_inputfield.
 DATA: l_id TYPE REF TO cl_htmlb_dropdownlistbox.
 l_ccode ?= cl_htmlb_manager=>get_data( request = runtime->server->request
 name = 'inputField'
 id = 'i_search' ).
 l_id ?= cl_htmlb_manager=>get_data( request = runtime->server->request
 name = 'dropdownListBox'
 id = 'ddname' ).
 ls_listvalue = l_id->selection.
 IF NOT l_ccode->value IS INITIAL.
 IF ls_listvalue = 'li_bukrs'.
 ls_name = l_ccode->value.
 ENDIF.
* Read Data into internal table by search term
 Select * from T001 into table gt_t001 where bukrs = ls_name.
 ENDIF.
WHEN 'tv_tabid'.
 DATA: tv_table TYPE REF TO cl_htmlb_tableview.
 DATA: table_event TYPE REF TO cl_htmlb_event_tableview.
 DATA: selectedrowindex TYPE i.
 tv_table ?= cl_htmlb_manager=>get_data( request = runtime->server->request
 name = 'tableView'
 id = 'tv_tabid' ).
 IF tv_table IS NOT INITIAL.
 table_event = tv_table->data.
 selectedrowindex = table_event->selectedrowindex.
* Read Table gt_t001 into Work Area and Pass the selected value through Navigator
 READ TABLE gt_t001 INTO wa_t001 INDEX selectedrowindex.
 navigation->set_parameter( name = 'nv_bukrs' value = 'samp').
 navigation->goto_page( 'FormRequest.bsp' ).
 ENDIF.
ENDCASE.
When I selected a row in the tableview, I am getting the selectedrow Index (selectedrowindex = table_event->selectedrowindex.). But the Values in the table gt_t001 are disapperiaring to read the contents by selectedrowindex.
Is there a way of capturing the contents of selected row or if I am doing any wrong in loosing the data from internal table.
Please help.

Hi Gireesh,
 I will give you a sample code which i have practiced for the same reqirement...
Oninputprocessing:
if event->name = 'tableView' and event->event_type = 'rowSelection'.
 data : data2 type ref to cl_htmlb_tableview.
 DATA: tv_data TYPE REF TO CL_HTMLB_EVENT_TABLEVIEW.
 data2 ?= cl_htmlb_manager=>get_data(
 request = request
 name = 'tableView'
 id = 'tview' ).
 clear tv_data.
 if not data2 is initial.
 tv_data = data2->data.
 clear wa1.
 read table it_mara3 into wa1 index tv_data->row_index.
 if sy-subrc = 0.
 v_matnr1 = wa1-matnr.
 call method navigation->set_parameter
 exporting
 name = 'v_matnr1'
 value = v_matnr1.
 navigation->goto_page( 'third.htm' ).
 endif.
 endif.
 endif.
where wa1 is a workarea declared as page attribute.
and every thing is correct in layout except one thing that i have added one more attribute to the tableview that is...
onNavigate="onMyNavigation"
ADD THE CODE WHAT EVER REQUIRED BY SEEING THE EXAMPLE GIVEN...YOU WILL GET THE SOLUTION.
Regards,
Azaz Ali.

Designer 9.0.2.7 - problems with capturing PL/SQL packages

Hello,
I would appreciate any help regarding the following issue:
We tried to capture in Designer 9.0.2.7 the existing PL/SQL packages from an Oracle 9i database and we have met some problems.
Even the package has a body containing two public procedures, when capturing, the Designer generates warnings that say the PL/SQL package body is empty. Therefore, the Designer capture the body content and write it in the PL/SQL Block of the PL/SQL Definition property, but the content of the body is preceded with the " character.
This makes problem when generating the "ddl" for the package (the package is not created correctly in the DB).
In addition, when generating the "ddl", the "END package_name" is added twice.
Other problem is that the package specification information from Designer is just "END package_name;"
For some of the packages containing only a list of public procedures, without any other variables declarations, the Designer does not capture these procedures as separate subprograms in the package definition, as it does other times. In this case, the package body is entirely captured in the PL/SQL Block and with the " character before content.
Is it some settings that can be done or some rules about the format of the PL/SQL procedures in order for Designer to capture all packages in same manner and correctly?
Thank you,
Claudia

Hi Keith,
I am connecting to the database as the package owner..
I have noticed earlier that I have problems when capturing triggers also.. The content of one large trigger contains 36371 characters and when capturing it from DB, the content was truncated to 28020 characters in Designer.
Our ideas with capturing the DB packages/procedures were to use the Designer as version control system.
We wanted to have all objects used in a project in Designer.. entities, tables, triggers, packages, procedures, Forms files, etc. in order to make a configuration for a project release.
Thank you,
Claudia

Problem in capturing excse invoice

Hi,
I am facing a problem while capturing excise invoice. I made goods receipt with reference to a single PO containing 3 line items by 101 mvt type. after that i reversed that document using mvt 102 for line item 2 and 3. Now the Original GR document contains only line item 1.
But while capturing Excise invoice with reference to the GR docuumber, system is showing message Document 9000005126 does not contain any selectable items.
Please suggest me how to capture excise invoices in the above scenerios.
Thanks
Prasant,

Prasant,
U said u have made 102 GR cancellation.While doing 102 mov type system will cancel whole document not 2 & 3 document.
So check whether this happened or not.
Thats why there is message of No selectable items.
Thanks & regards
Gitesh

Problem in Assigning table to access sequence

Dear All,
i am facing problem in assigning table to access sequence for billing output type.
I have created 1 table B902 with the combination of Sales org,plant ,Division,Billing doc type.
but if i am going to assign with access sequence system is taking for Billing type & division & for other its showing red marks & errorr.Access sequence->Aceessess->Field.if i am clicking on field in I/O column for plant its displaying negative.
bcause of this i am not able to make condtion record.
Message is Select a document field for WERKS
Regards
ajit
Edited by: SAP SD AJIT on Mar 1, 2010 3:18 PM

Hi SAP SD AJIT ,
Go to IMG --> Sales and Distribution --> Basic Functions --> Output control --> Output Determination --> Output Determination using condition technique --> Mantain output Determination for billing document --> Mantain condition table, in the pop-up choose the option "Field catalog: Messages for billing documents", there you can add standard field into the catalog, so you can add WERKS and the other one "document structure" I don't know what field it is, but if it is and standard field you can add it. If you have a Z field you need ABAP help to add the Z field to the structure "KOMKBZ5" and then you can add it to the catalog.
Regards,
Mariano.

Problem in creation table for sap 4.6

hello evrybody
i have just a problem in creating table with se11;after saving and activite those table and zhen i select icon of contents it bloocks and shoz this error message :
Error reading table TMCNV; RC = 4
Message no. BMG 135
thank you for your help
Edited by: Rob Burbank on Apr 6, 2010 10:20 AM

Seems like you have a material number field (domain with conversion routine MATN1 or alike) and table TMCNV does not have the entry with key 'MATCONV', check the where used-list of message BMG 135. I assume this entry comes delivered by SAP, so try to restore it.
Also search for OSS notes with "TMCNV" or "BMG 135".
Thomas

Problems with a table in PDF`S footer

Dear sirs,
We are having problems when trying to run a PDF with Adobe LiveCycle Designer tool.
We are working with a PDF which is composed of a header, the main body and a footer. We have created a table (table1) at the footer and
another one at the main body (table2). This last table (table2) may overflow therefore it will genarate two pages for our PDF.
On both pages appear the header and the footer correctly but in the last page it does not write the data from the table included in the footer (table1).
We have no problems with the table included in the main body
In the attachments, I send you the screenshots of both pages in which I have marked in red the part where we have error.
May you help us to solve our problem?
Thanks in advance your help.
Edited by: emgaitan on Mar 16, 2010 2:18 PM

Wardell,
Check the data in RSA3 for the extractor that you use to bring data .
You must be using the data source 0CO_OM_CCA_09. Check the data and reconcile and you will get it.
Let me know if you need anything else.
Thanks
Ravi Thothadri
[email protected]

Problem in joining tables

Hi All,
Here I am facing the problem in Joining table I have S031,s032,makt,marc,I need a field ATWRT field from CAWN table,I did't find any link for this above from tables, any one please help me how to find out.
REPORT ZMMTEST.
tables:s031,s032,makt,marc.
DATA : BEGIN OF itab1 OCCURS 0,
       matnr TYPE s031-matnr,
       lgort      TYPE s031-lgort,
       werks      TYPE s031-werks,
       spmon      TYPE s031-spmon,
       magbb      type S031-magbb,
       wagbb      type S031-wagbb,
       azubb      type S031-azubb,
       aagbb      type S031-aagbb,
       END OF itab1.
DATA : BEGIN OF itab2 OCCURS 0,
       matnr like makt-matnr,
       maktx like makt-maktx,
       END OF itab2.
DATA : BEGIN OF itab3 OCCURS 0,
       matnr TYPE marc-matnr,
       werks type marc-werks,
       ekgrp type marc-ekgrp,
       END OF itab3.
DATA : BEGIN OF itab4 OCCURS 0 ,
       matnr   TYPE s032-matnr,
       lgort   TYPE s032-lgort,
       werks   TYPE s032-werks,
       mbwbest type s032-mbwbest,
       wbwbest type s032-wbwbest,
       END OF itab4.
data : begin of itab5 occurs 0,
      objek   type ausp-objek,
       atwrt   type cawn-atwrt,
       end of itab5.
DATA : BEGIN OF itab_final1 OCCURS 0,
       matnr      TYPE s031-matnr,
       lgort      TYPE s031-lgort,
       werks      TYPE s031-werks,
       spmon      TYPE s031-spmon,
       magbb      type S031-magbb,
       wagbb      type S031-wagbb,
       azubb      type S031-azubb,
       aagbb      type S031-aagbb,
       maktx      TYPE makt-maktx,
       ekgrp      type marc-ekgrp,
       mbwbest    type s032-mbwbest,
       wbwbest    type s032-wbwbest,
       END OF itab_final1.
DATA : BEGIN OF itab_final OCCURS 0,
       matnr      TYPE s031-matnr,
       lgort      TYPE s031-lgort,
       werks      TYPE s031-werks,
       spmon      TYPE s031-spmon,
       magbb      type S031-magbb,
       wagbb      type S031-wagbb,
       azubb      type S031-azubb,
       aagbb      type S031-aagbb,
       maktx      TYPE makt-maktx,
       ekgrp      type marc-ekgrp,
       mbwbest    type s032-mbwbest,
       wbwbest    type s032-wbwbest,
       atwrt      type cawn-atwrt,
       END OF itab_final.
select-options:s_matnr for s031-matnr.
start-of-selection.
select matnr lgort werks spmon magbb wagbb azubb aagbb
        from s031 into table itab1
        where matnr in s_matnr.
if not itab1[] is initial.
    select matnr maktx from makt into table itab2 for all entries in itab1 where matnr = itab1-matnr.
if not itab2[] is initial.
   select matnr werks ekgrp from marc into table itab3 for all entries in itab2 where matnr = itab2-matnr.
if not itab3[] is initial.
   select matnr werks mbwbest wbwbest from s032 into corresponding fields of table itab4 for all entries in itab3 where matnr = itab3-matnr.
*if not itab4[] is initial.
   select atwrt from cawn into corresponding fields of table itab5.*
     endif.
   endif.
endif.
endif.
end-of-selection.
loop at itab3.
   itab_final-matnr = itab3-matnr.
   read table itab2 with key matnr = itab3-matnr.
   if sy-subrc = 0.
    itab_final-maktx = itab2-maktx.
   read table itab1 with key matnr = itab2-matnr.
   if sy-subrc = 0.
    itab_final-lgort = itab1-lgort.
    itab_final-werks = itab1-werks.
    itab_final-spmon = itab1-spmon.
    itab_final-magbb = itab1-magbb.
    itab_final-wagbb = itab1-wagbb.
    itab_final-azubb = itab1-azubb.
    itab_final-aagbb = itab1-aagbb.
endif.
   endif.
   itab_final-ekgrp = itab3-ekgrp.
read table itab4 with key matnr = itab3-matnr.
if sy-subrc = 0.
itab_final-mbwbest = itab4-mbwbest.
endif.
itab_final-wbwbest = itab4-wbwbest.
append itab_final.
clear itab_final.
endloop.
WRITE: /2 'material', 23 'storagelocation',29 'plant',35 'date',44 'val.stock.issue',66 'val.stock.issue.value',86 'no.of.stock.receipts',97 'no.of.stock.issues',150 'material.des', 160 'pur.group',190 'stock.val',210 'stock.quan'.
ULINE.
loop at itab_final.
WRITE: /2 itab_final-matnr, 23 itab_final-lgort,29 itab_final-werks,35 itab_final-spmon,44 itab_final-magbb,66 itab_final-wagbb,86 itab_final-azubb,97 itab_final-aagbb,
           150 itab_final-maktx, 160 itab_final-ekgrp,190 itab_final-wbwbest,210 itab_final-mbwbest,itab_final-atwrt.
ENDLOOP.
Thanks&regds,
Sree.

Hi sree,
take join between s031-sptag ,ausp-datuvthen fetch records based on this condition.(itab1)
After retrieve records based on join condition between
ausp-atinn,ausp-adzhl and cawn-atinn,cawn-adzhl.(itab2)
Retrieve records using for all entries bet first join condition and second join condition.
use for all entries between itab1 and itab2.
it will work surely.
reaward points

How to create the temp table in Sybase with values from Excel ?

Dear Sir/Madam,
I know this is not related with oracle DB, however i am in the need of help from you people who worked on Sybase. plz help me..
I have the excel sheet which contains EmpId and EmpName values. I just wanted to read these two values one by one from an excel sheet and loaded them into one temp table in Sybase. is it possible thru sqlldr ?
here is the sample code for your reference:
begin tran
create table tempdb..empIdName (emp_id int identity,emp_name varchar(50))
go
Awaiting for your valuable reply
thanks
pannar

there is some hint provided by sybase user
If it's Sybase IQ, you can export the excel file to a CSV file, then use a LOAD TABLE statement to get the data into your temporary table.
For ASE, BCP would provide similar functionality.
I am using ISQLW tool to work with sybase DB. what query to load the excel data to tem table in sybase. anyone who knows this? help me

Sorting Problem in FND_MENU_ENTRIES_TL Table

Hi,
FND_MENU_ENTRIES_TL Table storing the record FND_MENU_ENTRIES_TL_N1(MENU_ID,PROMPT,LANGUAGE) wise in R12. But whereas in 11i, records stored FND_MENU_ENTRIES_TL_U1(MENU_ID,ENTRY_SEQUENCE,LANGUAGE).
I am confused, whether i need to recreate the index in R12, so the records will get store MENU_ID,ENTRY_SEQUENCE,LANGUAGE wise.
Could any one please suggest me how to resolve this problem.
Thanks,
Praba T

815667 wrote:
Hi,
FND_MENU_ENTRIES_TL Table storing the record FND_MENU_ENTRIES_TL_N1(MENU_ID,PROMPT,LANGUAGE) wise in R12. But whereas in 11i, records stored FND_MENU_ENTRIES_TL_U1(MENU_ID,ENTRY_SEQUENCE,LANGUAGE).
I am confused, whether i need to recreate the index in R12, so the records will get store MENU_ID,ENTRY_SEQUENCE,LANGUAGE wise.
Could any one please suggest me how to resolve this problem.
Thanks,
Praba TPl do not abuse the forums by cross-posting in multiple forums
Sorting Problem in FND_MENU_ENTRIES_TL Table
Sorting Problem in FND_MENU_ENTRIES_TL Table
Your issue is related to EBS, not to database upgrades (which is the topic of this forum)
Srini

I am getting problem with internal table & work area declaration.

I am working with 'makt' table ..with the table makt i need to work with styles attributes ..so i declared like this
TYPES : BEGIN OF ty_makt,
         matnr TYPE makt-matnr,
         spras TYPE makt-spras,
         maktx TYPE makt-maktx,
         maktg TYPE makt-maktg,
         celltab TYPE lvc_t_styl,
       END OF ty_makt.
DATA : i_makt TYPE TABLE OF ty_makt.
DATA : wa_makt TYPE ty_makt .
    But end of program i need to update dbtable "makt"...i am getting problem with internal table & work area declaration.
i think makt table fields mapping and internal table/work area mapping is not correct. so please help me to get out from this.

Hi Nagasankar,
TYPES : BEGIN OF TY_MATNR,
              MATNR TYPE MAKT-MATNR,
              SPRAS TYPE MAKT-SPRAS,
              MAKTX TYPE MAKT-MAKTX,
              MAKTX TYPE MAKT-MAKTG,
              CELLTAB TYPE LVC_T_STYL, " Its Working perfectly fine..
             END OF TY_MAKT.
DATA: IT_MAKT TYPE STANDARD TABLE OF TY_MAKT,
          WA_MAKT TYPE TY_MAKT.
Its working perfectly fine. if still you are facing any issue post your complete code.
Thanks,
Sandeep

Problem to capture tables in Sybase 12.5 database

Similar Messages

Maybe you are looking for