ABAPxxxGoddess
You got it. Exactly like that.
Sorry about your Oracle guy. Of course, within the known SAP-universe, he's
right. DBCON is SAP's way of connecting to another database. This
array-method is something we had to invent here to get around the
performance problem, and it was a team effort of note, between experts in
all kinds of areas. Credits: Phil O'Rourke (Scotland), Ian Porter
(Scotland), Brian Wall (OracleXXXGod, Scotland), and myself. ^_^
When you're done, and breathing again, I'd love to know - what's /up/ with
that username? Is it to get faster responses to arcane questions?
On Mon, Oct 4, 2010 at 5:23 AM, stupid++ via sap-dev <
sap-dev@groups.ittoolbox.com> wrote:
>
>
> Dear,
>
> Try this, but do not miss use this as this can put your sap in inconsistent
> state.
> Open oracle SAP *Plus,
> log on in oracle with user: SAPXXX [XXX is SID No.] and Password:SAP or
> set
> at time of SAP Installation.
> Now run any query like
> SELECT * FROM TABLENAME; (eg select * from KNA1)
> or whatever you want to do. I hope It will solve your purpose.
>
> Regards,
>
> Vineet Kumar
> Programmer
> India
>
> vineet_erp skype, yahoo
>
>
> On Mon, Oct 4, 2010 at 9:03 AM, ABAPxxxGoddess via sap-dev <
> sap-dev@groups.ittoolbox.com> wrote:
>
> > Posted by ABAPxxxGoddess
> > on Oct 3 at 11:33 PM Hi
> > Mark,
> >
> > I have read again everything you've mentioned. I think I understand now
> the
> > idea you're sharing with. 'Coz the Oracle guys here (due to some
> policies, I
> > have to deal with them first before going to the DBA) kept on insisting
> that
> > I can just use that DBCON to send data to Oracle w/c led me more to
> > confusion trying to understand the Oracle side.
> >
> > So let me say, the idea is:
> > (1) first, connect to Oracle to execute the native sql. (exec
> > sql...endexec)
> > (2) from there, the treatment should be like you're already in an Oracle
> > environment
> > (3) so when you do the "insert into oracle_table select * from
> sap_table",
> > you're selecting data from an SAP table to Oracle. To make this possible,
> a
> > DBLink should be created at Oracle side (since you're already connected
> to
> > Oracle)
> >
> > Please let me know of any violent reactions, but I believe this is your
> > idea. I'll let you know once I succeed ^-^
> >
> > ---------------Original Message---------------
> > From: Mark von Delft
> > Sent: Friday, October 01, 2010 3:05 AM
> > Subject: Bulk insert SQL command to transfer data from SAP to Oracle -
> > CL_SQL_CONNECTION
> >
> > > Aaaargh, sorry, I missed a trick. Or more precisely, I missed a
> > > "disclaimer". The DB-link is a term your OracleXXXGod would understand,
> > but
> > > a SAP consultant wouldn't. It's *not* an entry in DBCON.
> > >
> > > You're using EXEC SQL, and you're *not* using DBCON. Darn, this is
> going
> > to
> > > be hard.
> > >
> > >
> > > What you're *not* doing (this is what you tried, and it failed, due to
> > > limitations in EXEC SQL).
> > > * you're not setting up a connection to the remote DB in DBCON
> > > * you're not calling EXEC SQL. OPEN CONNECTION xxx, SET CONNECTION xxx
> > >
> > > ---> Yes - normally you *do* need a DBCON to use EXEC SQL.
> > >
> > >
> > >
> > > What you *are* doing:
| __.____._ Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
| |  _.____.__ |
Mark as helpful
