Hello Mike, backint is a tool for backing up and restoring databases, it is no tool to import the left-overs of an Oracle database into a SAP DB database. You have to extract your data from the Oracle database into a non binary form and you have to load that data into the SAP DB using SAP DB's Loader.
Best Regards, Tilo Heinrich SAP Labs Berlin -----Original Message----- From: Michael Slinn [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2003 1:30 AM To: SAPDB General List Subject: backint for Oracle We want import our Oracle 8i database into SAPDB and then access it via JDBC.� The two files we have are called JspExplorer_data01.dbf and JSPEXPLORER_idx01.dbf.� Both files are 52,436,992 bytes, and they are binary files.� Oracle is not available to us any more. Seems like backint is the tool to use (present in /opt/sapdb/depend/bin/backint). $ /opt/sapdb/depend/bin/backint --help usage: /opt/sapdb/depend/bin/backint -u <user_id> [-f <function>] [-t <type>] [-p <par_file>] [-i <in_file>] [-o <out_file>] [-c] parameters can be: <user_id> : char(16) <function>: backup|restore|inquire|delete <type> : file <par_file>: char(255) <in_file> : char(255) <out_file>: char(255) $ /opt/sapdb/depend/bin/backint -u sapdb -f inquire -i /home/gblake/JspExplorer_data01.dbf Reading parameter file . No staging area is defined in the parameter file. The path of Backint for Oracle is not defined in the parameter file. The name of the history file is not defined in the parameter file. The name of the input file of Backint for Oracle is not defined in the parameter file. The name of the output file of Backint for Oracle is not defined in the parameter file. The name of the error output file of Backint for Oracle is not defined in the parameter file. I found a posting in German (which I could not read - http://listserv.sap.com/pipermail/sapdb.general/2002-June/012421.html) discussing a file called bsi.env, which I fiddled with, knowing that I was completely ignorant: BACKINT /opt/sapdb/depend/bin/backint/opt/sapdb/depend/bin/backint INPUT /home/gblake/JspExplorer_data01.dbf OUTPUT /var/opt/sapdb/indep_data/backint/JspExplorer.out ERROROUTPUT /var/opt/sapdb/indep_data/backint/Backint4Oracle.err PARAMETERFILE /var/opt/sapdb/indep_data/backint/backint.par TIMEOUT_SUCCESS 600 TIMEOUT_FAILURE 300 ORIGINAL_RUNDIRECTORY /var/opt/sapdb/indep_data/backint As far as I can tell, /var/opt/sapdb/indep_data/backint/backint.par should look something like: STAGING AREA: /var/opt/sapdb/indep_data/backint/STAGE1 1 GB STAGING AREA: /var/opt/sapdb/indep_data/backint/STAGE2 1024 MB FILES PER BACKINT CALL: 2 BACKINT: /opt/sapdb/depend/bin/backint PARAMETERFILE OF BACKINT: /var/opt/sapdb/indep_data/backint/backintparam.utl HISTORY FILE: /var/opt/sapdb/indep_data/backint/BackintHistory INPUTFILE FOR BACKINT: /home/gblake/JspExplorer_data01.dbf OUTPUTFILE FOR BACKINT: /var/opt/sapdb/indep_data/backint/JspExplorer.out ERRORFILE FOR BACKINT: /var/opt/sapdb/indep_data/backint/Backint4Oracle.err MAXIMAL DELAY OF BACKINT CALL: 30 I wonder how far off the mark I am? Is this possible? Mike _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
