Status: Unverified
SYMPTOM(s):
Getting error 1006 when running protoMSS in a batch mode
prodict/mss/_mss_md0.p Database DICTDB not connected. (1006)
FACT(s) (Environment):
The batch file contains the following information:
SET PRODBNAME=sp2k # progress source DB name
SET PROCONPARMS="-1 -i" # source DB connection parameter
SET SHDBNAME=msh # Schema holder name
SET MSSDBNAME=mssp2k # ODBC DSN Name
SET MSSPDBNAME=lsh # Logical name
SET MSSUSERNAME=dbo # MS SQL Server DB owner
SET MSSPASSWORD= # MS SQL Server password
SET MSSCONPARMS= # Additional connection parameters for the schema holder
SET MSSCODEPAGE=iso8859-1 # OE name for the code page that the ODBC data source uses
SET MSSCOLLNAME=basic # Collation name
SET MSSCASESEN=No # Yes or No code page sensitive
SET COMPATIBLE=Yes # Create arrays or recid
SET VARLENGTH=8000 # Total number of characters a VARCHAR can have
SET SQLWIDTH=NO # Use SQL-Width
SET LOADSQL=YES # To create tables on the MS SQL Server empty DB
SET MOVEDATA=NO # To populate Records on the MS SQL Server tables from Progress DB
SET UNICODETYPES=NO # Yes or No for unicode data type on the MS SQL Server, default is No
SET UNICODE_EXPAND=NO # Yes or No for the double the length on conversion, default is No
pro -b -p prodict/mss/protomss.p
MS SQL Server DataServer documentation does not mention the connection requirement to the Progress/OE source database
Progress 9.1x
OpenEdge 10.x
MS SQL DataServer
CAUSE:
Bug# OE00183240
CAUSE:
The sp2k Progress/OE source database is not connected despite the environment variable is set on the batch file
FIX:
The workaround is to specify the progress/OE source database on the batch file as
pro <path>\<db name> -b -p prodict/mss/protomss.p
Then save the changes and run the batch file again.
If you want to create the schema holder on a specific directory other then the current directory, use "cd <path of the directory you want>" without the double quotes at the beginning of the batch script so that path becomes working directory for the schema holder.
For instance:
######################### protoMSS Batch file START #########################
cd C:\temp
SET PRODBNAME=sp2k # progress source DB name
SET PROCONPARMS="-1 -i" # source DB connection parameter
SET SHDBNAME=msh # Schema holder name
SET MSSDBNAME=mssp2k # ODBC DSN Name
SET MSSPDBNAME=lsh # Logical name
SET MSSUSERNAME=dbo # MS SQL Server DB owner
SET MSSPASSWORD= # MS SQL Server password
SET MSSCONPARMS= # Additional connection parameters for the schema holder
SET MSSCODEPAGE=iso8859-1 # OE name for the code page that the ODBC data source uses
SET MSSCOLLNAME=basic # Collation name
SET MSSCASESEN=No # Yes or No code page sensitive
SET COMPATIBLE=Yes # Create arrays or recid
SET VARLENGTH=8000 # Total number of characters a VARCHAR can have
SET SQLWIDTH=NO # Use SQL-Width
SET LOADSQL=YES # To create tables on the MS SQL Server empty DB
SET MOVEDATA=NO # To populate Records on the MS SQL Server tables from Progress DB
SET UNICODETYPES=NO # Yes or No for unicode data type on the MS SQL Server, default is No
SET UNICODE_EXPAND=NO # Yes or No for the double the length on conversion, default is No
pro <path>\<source progress or OE DB> -b -p prodict/mss/protomss.p
#####.#################### protoMSS Batch file END #########################
.