Upgrading Gen 8.0 CSE database to Gen 8.6 

Running the CSE Configuration program cse_config.exe with options "Update Encyclopedia tables to this release" and "Update Coordination tables to this release" produces this message.

---------------------------
cse_config
Error 1 while running Encyclopedia initialization
OK  
---------------------------

Process Monitor revealed the following successful execution sequence

C:\windows\system32\cmd.exe /c ""D:\Program Files (x86)\CA\CA Gen 8.6\CSE\cse_msqls\prepbinenv.cmd" "D:\Logs\CA Gen 8.6\prepbinenv.log""
"osql.exe" -U GENUser -P ######## -D S_IEFDIRC -e -b -n -i "D:\Program Files (x86)\CA\CA Gen 8.6\CSE\cse_msqls\dbiefdirprc.sql" -o "D:\Logs\CA Gen 8.6\dbiefdirprc.log"
"sqlcmd.exe" -U GENUser -P ######## -d S_IEFDIRC -b -i "D:\Program Files (x86)\CA\CA Gen 8.6\CSE\cse_msqls\checkpswdcol.sql" -o "D:\Logs\CA Gen 8.6\pswdcol.txt"

This was followed by error status of 1 for this command

"D:\Program Files (x86)\CA\CA Gen 8.6\CSE\bin\initdir.exe" -c "DBNAME=S_IEFDIRC DBUSER=GENUser DBPSWD=########"  -l

If rerun the configuration with "Update Encyclopedia tables to this release" and "Skip Coordination tables configuration" the same symptom appeared:

---------------------------
cse_config
Error 1 while running Encyclopedia initialization
OK  
---------------------------

This time the successful execution sequence was

C:\windows\system32\cmd.exe /c ""D:\Program Files (x86)\CA\CA Gen 8.6\CSE\cse_msqls\prepbinenv.cmd" "D:\Logs\CA Gen 8.6\prepbinenv.log""
"osql.exe" -U GENUser -P ######## -D S_IEFDC -e -b -n -i "D:\Program Files (x86)\CA\CA Gen 8.6\CSE\cse_msqls\dbiefdprc.sql" -o "D:\Logs\CA Gen 8.6\dbiefdprc.log"
"osql.exe" -U GENUser -P ######## -D S_IEFDC -e -b -n -i "D:\Program Files (x86)\CA\CA Gen 8.6\CSE\cse_msqls\schemadeletetbls.sql" -o "D:\Logs\CA Gen 8.6\schemadeletetbls.log"
C:\windows\system32\cmd.exe /c ""D:\Program Files (x86)\CA\CA Gen 8.6\CSE\cse_msqls\loadschema.cmd" "D:\Program Files (x86)\CA\CA Gen 8.6\CSE\cse_msqls" dcvsds2071 S_IEFDC GENUser ######## "D:\Logs\CA Gen 8.6\loadschema.log" "D:\Logs\CA Gen 8.6\out_file.lst" "D:\Logs\CA Gen 8.6\err_file.lst""
bcp  S_IEFDC..SASC in sqssch90_asc.tbl -S dcvsds2071 -U GENUser -P ######## -b 100 -b 1000 -m 1 -c -e "D:\Logs\CA Gen 8.6\out_file.lst" -o "D:\Logs\CA Gen 8.6\err_file.lst"
bcp  S_IEFDC..SDIV in sqssch90_div.tbl -S dcvsds2071 -U GENUser -P ######## -b 100 -b 1000 -m 1 -c -e "D:\Logs\CA Gen 8.6\out_file.lst" -o "D:\Logs\CA Gen 8.6\err_file.lst"
bcp  S_IEFDC..SOBJ in sqssch90_obj.tbl -S dcvsds2071 -U GENUser -P ######## -b 100 -b 1000 -m 1 -c -e "D:\Logs\CA Gen 8.6\out_file.lst" -o "D:\Logs\CA Gen 8.6\err_file.lst"
bcp  S_IEFDC..SPRP in sqssch90_prp.tbl -S dcvsds2071 -U GENUser -P ######## -b 100 -b 1000 -m 1 -c -e "D:\Logs\CA Gen 8.6\out_file.lst" -o "D:\Logs\CA Gen 8.6\err_file.lst"
bcp  S_IEFDC..STRG in sqssch90_trg.tbl -S dcvsds2071 -U GENUser -P ######## -b 100 -b 1000 -m 1 -c -e "D:\Logs\CA Gen 8.6\out_file.lst" -o "D:\Logs\CA Gen 8.6\err_file.lst"
bcp  S_IEFDC..SASC in sqssch91_asc.tbl -S dcvsds2071 -U GENUser -P ######## -b 100 -b 1000 -m 1 -c -e "D:\Logs\CA Gen 8.6\out_file.lst" -o "D:\Logs\CA Gen 8.6\err_file.lst"
bcp  S_IEFDC..SDIV in sqssch91_div.tbl -S dcvsds2071 -U GENUser -P ######## -b 100 -b 1000 -m 1 -c -e "D:\Logs\CA Gen 8.6\out_file.lst" -o "D:\Logs\CA Gen 8.6\err_file.lst"
bcp  S_IEFDC..SOBJ in sqssch91_obj.tbl -S dcvsds2071 -U GENUser -P ######## -b 100 -b 1000 -m 1 -c -e "D:\Logs\CA Gen 8.6\out_file.lst" -o "D:\Logs\CA Gen 8.6\err_file.lst"
bcp  S_IEFDC..SPRP in sqssch91_prp.tbl -S dcvsds2071 -U GENUser -P ######## -b 100 -b 1000 -m 1 -c -e "D:\Logs\CA Gen 8.6\out_file.lst" -o "D:\Logs\CA Gen 8.6\err_file.lst"
bcp  S_IEFDC..STRG in sqssch91_trg.tbl -S dcvsds2071 -U GENUser -P ######## -b 100 -b 1000 -m 1 -c -e "D:\Logs\CA Gen 8.6\out_file.lst" -o "D:\Logs\CA Gen 8.6\err_file.lst"
bcp  S_IEFDC..SASC in sqssch92_asc.tbl -S dcvsds2071 -U GENUser -P ######## -b 100 -b 1000 -m 1 -c -e "D:\Logs\CA Gen 8.6\out_file.lst" -o "D:\Logs\CA Gen 8.6\err_file.lst"
bcp  S_IEFDC..SDIV in sqssch92_div.tbl -S dcvsds2071 -U GENUser -P ######## -b 100 -b 1000 -m 1 -c -e "D:\Logs\CA Gen 8.6\out_file.lst" -o "D:\Logs\CA Gen 8.6\err_file.lst"
bcp  S_IEFDC..SOBJ in sqssch92_obj.tbl -S dcvsds2071 -U GENUser -P ######## -b 100 -b 1000 -m 1 -c -e "D:\Logs\CA Gen 8.6\out_file.lst" -o "D:\Logs\CA Gen 8.6\err_file.lst"
bcp  S_IEFDC..SPRP in sqssch92_prp.tbl -S dcvsds2071 -U GENUser -P ######## -b 100 -b 1000 -m 1 -c -e "D:\Logs\CA Gen 8.6\out_file.lst" -o "D:\Logs\CA Gen 8.6\err_file.lst"
bcp  S_IEFDC..STRG in sqssch92_trg.tbl -S dcvsds2071 -U GENUser -P ######## -b 100 -b 1000 -m 1 -c -e "D:\Logs\CA Gen 8.6\out_file.lst" -o "D:\Logs\CA Gen 8.6\err_file.lst"
"osql.exe" -U GENUser -P ######## -D S_IEFDC -e -b -n -i "D:\Program Files (x86)\CA\CA Gen 8.6\CSE\cse_msqls\piviews.sql" -o "D:\Logs\CA Gen 8.6\piviews.log"

This was followed by error status of 1 for this command

"D:\Program Files (x86)\CA\CA Gen 8.6\CSE\bin\initdb.exe" -c "DBNAME=S_IEFDC DBUSER=GENUser DBPSWD=########"  -p 1 -r  -l

NOTE: ODBC Data Source Names (DSN) have been defined for the 2 databases for both 32-bit and 64-bit per the documentation:

CA GEN 8.6 > Encyclopedia > Client Server Encyclopedia > Using the Client Server Encyclopedia > Installing and Configuring CSE > Prerequisites for CSE Configuration > Configure Databases
- see "Create Microsoft SQL Server CSE Database"

Release : 8.6
Component : CA Gen Client Server Encyclopedia

In the ODBC Data Source Administrator (32-bit) program enabled Tracing which provided the root cause of the initdir.exe/Coordination database error:

initdir 11b4-9e8 EXIT SQLExecDirect with return code -1 (SQL_ERROR) HSTMT 0x011D8498 UCHAR * 0x6931CEA8 [ -3] "{call SQDIRXCPAPI_CPoAllR$3}\ 0" SDWORD -3 DIAG [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]The EXECUTE permission was denied on the object 'SQDIRXCPAPI_CPoAllR$3', database 'S_IEFDIRC', schema 'dbo'. (229) DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]The cursor was not declared. (16945)

The error for the initdb.exe/Encyclopedia database would likely be the same, just for a different stored procedure.

The SQL Server DBA resolved the permission problems.