BW SQL Source System using DBCON

I have created the Source system as mentioned in help.sap.com, and when I try to select Tables, it tell me that their are no tables.
But I wrote an ABAP program and tested the connection is working and I was able to pull data from one of the tables using ABAP.
I will appreciate if somebody can tell me what I am doing wrong.
Thanks
JAgraj Dhillon

Hi,
If you want to create a connection to an external database, you need relevant knowledge and experience of the source database in the following areas:
Tools,Database-specific SQL syntax,Database-specific functions
You also need relevant knowledge of the source application, in order to be able to transfer semantically utilizable data into the BW.
Before you are able to use the DB Connect functions, you need to have installed a database-specific DB client for the respective source-database management system (DBMS) on the BW application server, providing that the BW DBMS and the source DBMS are different.
In all cases, you need to license the database-specific DB client with the database manufacturer. You can get information about the database-specific DB client from the respective database manufacturers.
In addition, the SAP-specific part of the database interface - the Database Shared Library (DBSL) - must be installed for the corresponding source database management system on the BW application server
With DB Connect, you can load data from a database system that is supported by SAP, by
· linking a database to the BW as a source system, thereby creating a direct point of access to external relational database management systems (RDBMS).
· making metadata known to the BW by generating a DataSource
Hope it helps!!

Similar Messages

System Copy Guide: Exporting the Source System Using SAPinst.

Hi Gurus,
I am trying to do Unicode conversion of ERP 2005 SR3 on Oracle/WS2003
The preparation steps are OK
When I execute the last Phase using Sapinst : "database instance export",
it finishes within one minute with the message "Database instance export has been completed succesfully"
but without exporting data.
I have follow up Unicode Conversion Guide and System Copy Guide System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 ABAP+Java.
What could be wrong here?
Thansk for your help
Martial

So you need to set an environment variable
SAPINST_USE_HOSTNAME = <your-virtual-hostname>
for the user executing sapinst.
Markus

No username of Source system is avbl after livecache system copy

Hi Experts
I have done a livecache system copy from the source system to target system. Here the steps are
Assume my Source SYstem Livecache is RP1 and Target System livecache is RS1.
1. Taken Source system livecache DATA and LOG Area backup RP1.
2. Defined the same source system backup medium name in Target System (RS1 and moving the Source system Liveacache backuped files to Target system and defined the medium name as per that)
3. put the livecache db_admin mode
4. db_activate RECOVER <medium_name>.
5. recover_start <log_medium_name> LOG <nnn>
6. db_online.
Here we faced that
ERR
-24622,ERR_AUTOLOADSYSTAB: Automatic loading of the System Tables failed
-24907,ERR_DBAWRONG: Wrong database system administrator
-24988,ERR_SQL: SQL error
-4008,Unknown user name/password combination
So we activated the SUPERDBA as " db_activate SUPERDBA,<password>
then it came to online. and afterwards we have used the load_systab command to load the tables.
BUT we could not find any Source System name like "RP1ADM" in the tables of the livecache database. Only there are CONTROL,SUPERDBA username availbale. Usually there will be also the source admin name . I dont know why it is missing
Before a month we have done livecahe restore same as now in that time we got the source system name admin also. ( RP1ADM) and also tables which owned by RP1ADM. alos i could find APPSYSPARAM table and the instance also registered.
But now in this restore we could not find the above.
We followed the same procedure and there is no change in the steps also.
Could anyone help me...
Regards
bala

Hello Bala,
1. As I wrote you already, the notes:
886103 System Landscape Copy for SAP SCM
877203     Post steps after the Homogenous liveCache copy using backup/
457425     Homogenous liveCache copy using backup/restore
has all recommended steps to do, when you will run the u201CSystem Landscape Copy for SAP SCMu201D
2. If you run the u201CHomogenous liveCache copy using backup/restoreu201D you should pay attention to the note 457425. After you imported the complete data backup < step 2. > you need to update the system tables.
To update the system tables you need to know the correct database SYSDBA user & password.
After you restored the databackup of the source database, start the database online & run u201Cselect * from usersu201D SQL command to see the SYSDBA user. Then check that you know the DBA user ( DataBase Administrator ) & password of the source database instance => Open the SQL session with this
user & password.
Example:
after db_activate recover <medium_name>
login as control,password
db_online
sql_execute select * from users
sql_connect superdba,<password of source system>
If you didnu2019t get error with the last command, then you could update the system tables with the superdba,<password of source system> using load_systab command.
The system tables will be updated & the correct SYSDBA user & password will be updated in *.UPC file.
3.
user_sysdba:
You make the database system administrator known to Database Manager. It is only necessary to use this DBM command if the database administrator is not known or is incorrectly known to Database Manager.
u201CI have tried like this
after db_activate recover <medium_name>
login as control,password
db_admin
user_sysdba superdba,<password of source system>
db_onlineu201D
You could update the .upc files with the wrong SYSDBA user password u2026
You was lucky, that you knew the correct SYSDBA user and password of the source database.
Example < NLK is my local database >:
A.     I could update the .upc file with wrong password of SYSDBA user:
dbmcli -d NLK -u control,control
dbmcli on NLK>user_sysdba superdba,test
OK
dbmcli on NLK>db_online
OK
dbmcli on NLK>load_systab
ERR
-24909,ERR_DBAUNKNOWN: SYSDBA unknown
dbmcli on NLK>exit
B. I could update the .upc file with wrong SYSDBA user:
dbmcli -d NLK -u control,control
dbmcli on NLK>user_sysdba test,test
OK
dbmcli on NLK> user_get test
OK
u2026
dbmcli on NLK>sql_connect test,test
ERR
-24988,ERR_SQL: SQL error
-4008,Unknown user name/password combination
dbmcli on NLK> dbmcli on NLK>sql_connect superdba,admin
OK
I could connect as test,test; but the test user is NOT SYSDBA user u2026
dbmcli -d NLK -u test,test
dbmcli on NLK>
Itu2019s recommended to user the load_systab command, so the .upc files will be updated with the correct SYSDBA user/password or
you will get error.
4. http://maxdb.sap.com/doc/7_7/86/68627a1bc642e6a6f73d3bc7a55fe1/content.htm
You got error:
ERR
-24622,ERR_AUTOLOADSYSTAB: Automatic loading of the System Tables failed
-24907,ERR_DBAWRONG: Wrong database system administrator
-24988,ERR_SQL: SQL error
-4008,Unknown user name/password combination
The automatically updating the system tables, according to the default value, is switched on.
After you will run the update system tables with the correct SYSDBA user & password the *.UPC file will be updated,
and with the next liveCache restart you will not get this error.
5. See more information in the MAXDB library:
http://maxdb.sap.com/doc/7_7/45/11cbd6459d7201e10000000a155369/content.htm
Thank you and best regards, Natalia Khlopina
Edited by: Natalia Khlopina on May 19, 2010 2:58 PM

Extract data from Flat file CSV to SQL Server 2008 using SSIS 2008 (Data gets corrupted when extraction)

Hi,
I am trying to extract data from multiple CSV files to SQL into a single table. The data type of all the columns in SQL table is nvarchar(MAX). I am able to extract the data from the flat files but some of the data(on extraction) is
corrupt including question marks(?) and other invalid special characters. Also I tried selecting the UTF-8, 65001(Unicode) format but the problem still persists. Also I tried using data converter but no use.
I checked with the data in the flat file but there is no data with question mark(?) or any other special characters.
The separator in the flat file is Comma(,)
Please help.
Thanks in advace.

The source system and application determines the code page and encoding. Is it Windows, Unix, Mainframe or some other type?
Unicode files sometimes begin with a byte order mark (2 bytes) to indicate little or big endian. If you open the file in notepad and then select save as, the encoding in the dialog will show the encoding notepad detected based on the BOM. If
that is ANSI instead of Unicode or UTF-8, you will need to know the code page the source system used when the file was created.
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

Error is data loading from 3rd party source system with DBCONNECT

Hi,
We have just finished an upgrade of SAP BW 3.10 to SAP NW 7.0 EHP1.
After the upgrade, we are facing a problem with data loads from a third party Oracle source system using DBConnect.
The connection is working OK and we can see the tables in the source system. But we cannot load the data.
The error in the monitor is as follows:
'Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.'
But, unfortunately, the error message has no further information.
If we look at the job log in sm37, the job finished with the following log -
27.10.2009 12:14:19 Job started                                                                                00           516          S
27.10.2009 12:14:19 Step 001 started (program RSBATCH1, variant &0000000000119, user ID RXSAHA)                    00           550          S
27.10.2009 12:14:23 Start InfoPackage ZPAK_4FMNJ2ZHNNXC6HT3A2TYAAFXG                                              RSM1          797          S
27.10.2009 12:14:24 Element NOAUTHORITYCHECK is not available in the container                                     OL           356          S
27.10.2009 12:14:24 InfoPackage ZPAK_4FMNJ2ZHNNXC6HT3A2TYAAFXG created request REQU_4FMXSQ6TLSK5CYLXPBOGKF31G     RSM1          796          S
27.10.2009 12:14:24 Job finished                                                                                00           517          S
In a BW 3.10 system, there is no message related to element NOAUTHORITYCHECK. So, I am wondering if this is something new in NW 7.0.
Thanks in advance,
Rajib

There will be three things to get the errors like this
1.RFC CONNECTION FAILED
2.CHECK THE SOURCE SYSTEM
3.CHECK IT OUT WITH Oracle Consultants WEATHER THEY ARE FILLING UP THE LOADS.TELL THEM TO STOP
4.CHECK I DOC PROCESSING
5.FINALLY MEMORY ISSUES.
6.CATCH THE DATA SOURCE FIRST CHANGE IT AND THEN ACTIVATE AND RUN THE LOAD
7.LAST IS MEMORY ISSUE.
and also Check the RFC connection in SM59 If it is ok then
check the SAP note : 692195 for authorization
Santosh

Source system change

Hi,
Just a quick overview of our situation,
After the installation of BI development system (BID: 100) it was connected to the ECC dev system (ECD: 120).
Few months later, functional guys requested to change the source system connection from ECD: 120 to the new client in ECD system (i.e. ECD: 130).
But instead of using BDLS for the conversion, our team has created one more source system in the BID system for ECD: 130 client.
Now we have two entries in RSA1.
ECDCLNT120
ECDCLNT130 ..(new entry created by our team)
Now, we want to correct this situation. So now we have decided to follow the below steps.
1. Delete the client 130 connection from RSA1 and confirm that all references to client 130 have been deleted.
2. Run BDLS in BIW system to convert client 120 to 130
3. Re-establish the connection from BID to client 130 (SM59, WE21, WE20, RSA1 etc)
4. Establish the connection using "Restore" and test it.
5. Replicate and reactivate all transfer structures and data sources.
Regarding the first step, what exactly happens when someone delete the source system using RSA1.
Will this process deletes all info packages, data sources etc. associated with the source system ECD: 130?
Will there be any impact on the infopackages, process chains etc. related to the old source system ECD: 120?
As per some of the SDN threads/past experience, it might be possible that we could lose our custom (Z) infopackages, datasources after the source system deletion.
Could you please confirm this? And also verify above approach and suggest the best way in our case.
Thanks,
Tushar

Hi Tushar,
Regarding the first step, what exactly happens when someone delete the source system using RSA1 ?
It deletes all entries in the table :RSBASIDOC
Following entries are deleted at table level
RSBASIDOC record BI + R/3 Deleted
Technical connection optional
Partner profiles BI + R/3 deleted
Port definitions BI + R/3 deleted
Basis Idoc type BI + R/3 deleted
Dependent objects BI + R/3 deleted
Hope this helps.
Regards,
Mani

ABAP logical source system

dear all,
how can i get the logical source system using abap into my update rule?

Hello,
I believe is SY-SYSID.
Diogo.

R/3 Source system creation for BW

Hi Guru's,
How to create R/3 Source system in BW3.5(Version:IDES) of logical system name- T90CLNT090.
Please tell me what shud be the IP Address and Login details (Userid= ALE_MASTER). If possible plz give me the Password for user ALE_MASTER.
Points will be rewarded those give all the answers for questions mentioned above.
Thank you.

Hi Harshal,
You can choose to create a new R/3 source system using the first option (Automatic Creation). Here, you create a new destination and give the details of the new server details (your IDES system). This will create all the necessary ports and connections.
Here, you will need to create a system user (ALE_MASTER in your case). Setup this user as a system user in transaction SU01 before you start creating the connection to the new system. Create this user in both systems (BW and IDES).
Password for ALE_MASTER can be anything you set. Just remember the password if any maintenance of this user is needed in future.
Hope this helps.
Thanks and Regards
Subray Hegde

Error deleting source system with error message: "incorrect input for....."

Hi,
I'm trying to delete the source system using tcode RSA1 => Source systems => select the 'source system' and delete, but I got an error message as follows:
"incorrect input for activating transported shadow IPacks"
Fyi, I have opened up the client configuration (SCC4) prior to delete this source system but the source system still cannot be deleted and I receive the above error message.
Please let me know what is the caused of the error and how to solve the problem.
Thanks for your kind help.
Regards,
Mark

Hi Mark,
Which version of BW are you in?
check this thread and also the note 709581
Error Deleting Source system connection
Thanks,
Raj

How to create a DB Source system in BW

Hi Guys,
Can anybody explain me how to create DB Connect source system in BW.
Points will be awarded.
Thanks,
Chinna

Hi Chinna,
Below are the steps to be followed for the SS creation in BW :
Prerequisites :
1.System Number
2.System IP address
3.ALEOLTP like userid and password this is the RFC user ID in the R/3 system. Usually set to communication - must be set to dialog in the R/3 Source System for the duration of the create/restore connection process. Note: the password must be in capital letters.(If all instances are in unicode system)
1.At the time of making the connection, the R/3 source system will need to be opened for client independent configuration.
2.If it is a connection create or restore, the personal userid of the person doing the work must have SM59 access.
Follow the naming convention which is being used in your system.
1.     Logon to r/3 source system using the r/3 RFC userid to check that the userid has been set to dialog user. It is mandatory that the r/3 source system userid be setup temporarily as dialog to create the connection. If not contact the requester to have this done before continuing with the next step.
Note: When re-checking to ensure that the r/3 userid is a dialog user, you may get prompted for new password. Change password, and make a note of the new password. Use this new password in the steps that follow for the r/3 RFC userid.
2.     Logon to BW system using your own userid.
3.     Enter transaction RSA1, In Source Systems, right-click on Source Systems as shown below to create new connection.
4.     In the screen select the appropriate Source System connection type. Suppose your are creating connection for r/3 instance, so in this case we pick the very first option.
5.     A popup window will get displayed asking for the necessary information. To fill in the appropriate information in the that screen you need the following information concerning the r/3 source system.
     IP address (Application Server) &
     System Number
Get this information for the r/3 source system from the SAP Logon Pad.
6.     If Parameters have been incorrectly entered then the following error message will appear : Check connection parameters for the source system.
7.     Re-check and re-enter correctly. If all is good then You will see the following prompt : Please log on as an administrator in the following screen.Click green check to continue.
8.     This will bring you to the r/3 logon screen. Logon using the r/3 RFC id. Once logged on click Check in Check RFC destination dialog box.
9. Consider the r/3 RFC destination screen.
10. Check to make sure that BW system information (Userid, IP address, System Number etc) is correctly showing in the Technical Settings and Logon/Security tabs. Next do the following,
     Step 1: Enter password for the BW RFC userid id.
     Step 2: Save Settings
     Step 3: From Test Menu , click on authorization. Ensure there are no errors
     Step 4: Back out of screen.
11.     System may ask you to logon as administrator again. Logon as in Step 10. This time click on Use in Check RFC destination dialog box.
Connection related processing will start up at this time, and continue for a little while (can be a couple minutes or more).
12.     Subsequently, a dialog box will show up on the screen.
13. Pick option, Replicate As Well.
Replication and activation of data sources & transfer structures will begin.
With the completion of this step you will have successfully established this source system connection. To confirm, right-click on the new source system entry and click on check
14. If the connection is good, the following message with the source system ID will display at bottom left corner of screen : Source system connection is Ok.
Hope this will be helpful to you.
Thanks & Regards,
suchitra.V

Creating multiple source systems one logical system

Hi,
The requirement is to create two source systems using same logical name and different RFC connections to ECC?
We wanted to do some regular activities using one source system and some drill down activities using different source system.
I am getting error when I try to create second source system "source system already exist"
Please advice.
Thanks.

Hi,
I dont think it is possible to create multiple source systems in a sinle logical client. You have to create multiple clients and you can connect to BI system by different RFCs.
Hope this helps.....
Regards,
Suman

How to delete source system in BI system

Dear Experts ,
recently we finished client copy in BI production system to quality system,
now we are facing problem with source system connections in bI system
in RSA1 APO production system's source system is comes to BI quality system now i need to delete that APO source system in BI quality system ..please let me the process how can i delete source in BI quality
can i delete it as below
log in into BI quality system --> RSA1 --> select source system which i need to deletse --> right click & delete
or we have any other process to delete it.
Regards

Hi Swathimatta,
Apart from the two ways to delete the source system:
1.- log in into BI quality system --> RSA1 --> select source system which i need to deletse --> right click & delete
2.- Execcuting the FM 'RSAP_BIW_DISCONNECT.
If you cannot delete the source system:
Use fuction module RSAR_LOGICAL_SYSTEM_DELETE to delete
the source system:
1 - Go to SE37.
2 - Run fuction module RSAR_LOGICAL_SYSTEM_DELETE.
3 - Fill with the parameters as mentioned below:
      I_LOGSYS          = FUENTE
      I_FORCE_DELETE    = X
      I_NO_TRANSPORT    =
      I_NO_AUTHORITY    =
Or follow the recommendations from note 140276, Solution 2:
"You cannot delete the source system. Two cases have to be distinguished:
    o The source system still exists.
       Switch to Transaction SM59. Find the destination which has the
       same name as the logical system of the source system from field
       SLOGSYS in table RSBASIDOC (see above).
       - Such a destination does not exist in Transaction SM59. In this
          case, you have to create the destination to the source system.
          Name the destination equal the entry in SLOGSYS from above.
          Then return to the Administrator Workbench and repeat the
          deletion.
       - The entry exists but a remote login is not possible. Correct
          the communication parameters.
       - Everything works. Change to Transaction SE37, function module
          RSAR_LOGICAL_SYSTEM_DELETE, Sngl. test. Parameter I_LOGSYS =
          <log. name of the source system>, I_FORCE_DELETE = 'X'.
    o The source system no longer exists or was replaced with another
       source system with the same IP address.
       Proceed as described in the first case but make sure, that the
       field 'Target host' contains a not existing server in the
       maintenance screen of the destination (Transaction SM59). If
       necessary, change an existing entry. Later when you delete, the
       system asks you whether you want to delete, although the source
       system is not available. Select 'Ignore'. "
I hope it can help you.
Regards,
Fran.

No IDOCS arrived from Source system to BI for generic extraction

Hi All,
While loading data from r\3 generic data source to BI, I am facing the below problem.
1. Using Full Load:-
The request from r\3 to psa turns red after a while. The request monitor says:
Error when updating Idocs in Source System
Diagnosis
Errors have been reported in Source System during IDoc update:
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Source System . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
Details Tab shows : request green
Under that Extraction tab shows red
missing messages.
Transfer (IDocs and TRFC): Errors occurred .
Request IDoc : Application document not posted
I ran Transaction BD87,BD73 and execute with proper selections.
Upon checking the idoc in source system Their status is 51 , which says
Diagnosis
The control parameters for communication with the BW server are not
complete. A BW PlugIn upgrade could be the cause of the problem.
System response
Procedure
Depending on the Release of the BW server, proceed as follows:
BW Server Release 1.2B: Source system: Update InfoSource metadata
BW Server Release >= 2.0A: Source system: Activate.
Manually i tried to push the idocs in the BW and source system using TRF but i dint found any records???
Soruce system connection is fine. Profile parameters are set properly and its active .. But still am getting the same problem.
Many thanks, I'll applicate your help.!
Rakesh

Hi
I am also facing the same problem. This happened after restoration of the original system with a copy of the production.
I am not able to get the IDOC posted in the source R3 system.
I did a debug and it failed when verifying the table, RSBASIDOC.
There appeared to be some missing records which need to be inserted.
I can't find a way to insert the missing record and since then, I am not able to proceed.
Have you resolved the issue?
can you share how it can be overcome?
Thanks a lot

Standards around source system changes

Hello,
This is a general post around good practices to catch source system changes before they impact universes and reports
We have several universes built on source systems and generate user reports
The challenge we face is that there are many changes to these source systems that end up affecting the schema or flow of data. Source teams operate on a best endeavors policy to let us know if any of these impact universes/reports, but many times we discover the impact after the change.
Is there a way to design an automated check or process to proactively check or let us know whenever underlying source systems change from a BO universe stand-point? Are there any tools that can flag such concerns?
I am aware that this is a fairly open question, i am hoping to get advice from seasoned gurus who might have been in similar situations.
Regards

R S,
The only thing I can think of, is not using the same database as your source systems uses.
Instead, use data services to export the data to your own database, specific for reporting. And inside DS you can make it send out emails whenever something did not go as expected (table change, data type change, table renamed).
Your load process from the system database will stop when something like this, but at least it won't effect the reporting side (BO).
This idea on it's own is an entire project and a big one, so I don't know if would be what you are looking for.
Best
Leandro

Activating transfer rules for new source system

Hi
we are having 2 R/3 source system in BI. I had activated all the transfer rules with the first source system and now i have created a new source sytem connecting to a different R/3 client. I tried to change the transfer rules point to the new source system using the program RS_TRANSTRU_ACTIVATE_ALL giving the new source system and the infosource name. But i get the error "No Transfer Structure Selected" when i execute the prg.
how can i change the source system without creating the transfer rules for the new source but use the existing transfer rules and just change the source system assigned to it????
Regards
Sujai

Hi Sujai,
There are many cases when this program is used.
When the Trans rules get de-activated due to impact,we need to first replicate the data source and activate the TR using this program.This generally occurs during the data loads in prd.
It does not makes sense to transport it when there r no changes done to the TR.So simply,u can use this program to activate.
If the program does not work,then you are left with the transport option.
Thanks & Regards,
Suchitra.V

BW SQL Source System using DBCON

Similar Messages

Maybe you are looking for