Topic
  • 3 replies
  • Latest Post - ‏2014-03-27T17:30:43Z by KBCALL
KBCALL
KBCALL
7 Posts

Pinned topic Can't create a new Schema Repository

‏2014-03-26T15:00:55Z |

I just recently upgraded to 8.01 and tried to create a new Schema Repository.  However, the creation of the repository will not finish.  I receive the following error:

Copying tables:
master_global
Error: CRMDB0001E SQLExecDirect: RETCODE=-1, State=37000, Native Error=-3504
[Microsoft][ODBC Microsoft Access Driver] The SELECT statement includes a reserved word or an argument name that is misspelled or missing, or the punctuation is incorrect.
SQL statement="select  from master_global"

It appears to me that they have back SQL statement.  Missing the column list or a "*" in the select statement.  Has anyone run into this before and if so were you able to get around it to successfully create a new schema repo?

Full Error message is below and i am using MS SQL 2008 as the DB engine.

Creating the Master Repository...

*********************************************************************
Creating database CQ_GTS_MASTER_01 on server lewsql63:
 
   Vendor Type       : SQL_SERVER
   User name          : CQ_ADMIN
   Password            : ********
   Admin name        : CQ_ADMIN
   Admin password  : ********
 
*********************************************************************
 
Verifying data code page support for Master database; 1252 (MS Windows Latin 1) character set.
Setting Master database to platform code page; 1252 (MS Windows Latin 1) character set.
Set Master database code page to 1252 (MS Windows Latin 1) character set.
Validating destination location...
Logging on to source...
Logging on to destination...
Initializing schema...
 
Copying tables:
master_global
Error: CRMDB0001E SQLExecDirect: RETCODE=-1, State=37000, Native Error=-3504
[Microsoft][ODBC Microsoft Access Driver] The SELECT statement includes a reserved word or an argument name that is misspelled or missing, or the punctuation is incorrect.
SQL statement="select  from master_global"
 
 
NOTE: The complete execution log has been saved in C:\Users\kbcall\AppData\Local\Temp\cqdbsetup_status_20140326_0821_29.txt for your reference.
  • pradpara
    pradpara
    5 Posts

    Re: Can't create a new Schema Repository

    ‏2014-03-26T17:51:40Z  

    Hi KBCALL,

    You might want to have a look at the below technote which describes the problem,

    http://www-01.ibm.com/support/docview.wss?uid=swg21239777

    Most likely this should resolve your issue. If not, you might need to see if you followed the configuration mentioned in the below technote,

    http://www-01.ibm.com/support/docview.wss?uid=swg21377521

    Thanks

  • GlennSkinner
    GlennSkinner
    58 Posts

    Re: Can't create a new Schema Repository

    ‏2014-03-26T18:38:12Z  
    • pradpara
    • ‏2014-03-26T17:51:40Z

    Hi KBCALL,

    You might want to have a look at the below technote which describes the problem,

    http://www-01.ibm.com/support/docview.wss?uid=swg21239777

    Most likely this should resolve your issue. If not, you might need to see if you followed the configuration mentioned in the below technote,

    http://www-01.ibm.com/support/docview.wss?uid=swg21377521

    Thanks

    Pradpara is correct, the error code is misleading. Either you did not set the default schema to be the same name as the database owner, or I have seen in a few cases where you set the default schema correctly for the user under Security->login, but the schema does not get associated to the user if you look under Databases-><database>->Security->users.  I have only seen the latter a few times. If that does occur, the fastest fix is to delete the database and recreate it.

  • KBCALL
    KBCALL
    7 Posts

    Re: Can't create a new Schema Repository

    ‏2014-03-27T17:30:43Z  
    • pradpara
    • ‏2014-03-26T17:51:40Z

    Hi KBCALL,

    You might want to have a look at the below technote which describes the problem,

    http://www-01.ibm.com/support/docview.wss?uid=swg21239777

    Most likely this should resolve your issue. If not, you might need to see if you followed the configuration mentioned in the below technote,

    http://www-01.ibm.com/support/docview.wss?uid=swg21377521

    Thanks

    Thanks for the link.  This solved the issue.