[ 
https://issues.apache.org/jira/browse/TRAFODION-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roberta Marton closed TRAFODION-1238.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0-incubating

Fixed after release 1.1 was released and before moving to Apache release.

> LP Bug: 1455585 - Error 1234 returned trying to run SQL requests
> ----------------------------------------------------------------
>
>                 Key: TRAFODION-1238
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-1238
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: sql-security
>            Reporter: Roberta Marton
>            Assignee: Roberta Marton
>            Priority: Blocker
>             Fix For: 2.0-incubating
>
>
> After merging with https://review.trafodion.org/1635, I get the following 
> error when trying to run a query through sqlci:
> showddl user1.games;
> *** ERROR[1234] Authorization need to be reinitialized due to missing or 
> corrupted privilege manager metadata. To reinitialize, do 'initialize 
> authorization, drop' followed by 'initialize authorization'. This deletes and 
> recreates privilege manager metadata. Trafodion metadata is not affected.
> *** ERROR[2235] Compiler Internal Error: An unknown error, originated from 
> file ../arkcmp/CmpContext.cpp at line 515.
> *** ERROR[8822] The statement was not prepared.
> Following the directions in the message, I try running initialize 
> authorization, drop unsuccessfully:
> initialize authorization, drop;
> *** ERROR[1234] Authorization need to be reinitialized due to missing or 
> corrupted privilege manager metadata. To reinitialize, do 'initialize 
> authorization, drop' followed by 'initialize authorization'. This deletes and 
> recreates privilege manager metadata. Trafodion metadata is not affected.
> *** ERROR[1234] Authorization need to be reinitialized due to missing or 
> corrupted privilege manager metadata. To reinitialize, do 'initialize 
> authorization, drop' followed by 'initialize authorization'. This deletes and 
> recreates privilege manager metadata. Trafodion metadata is not affected.
> *** ERROR[1234] Authorization need to be reinitialized due to missing or 
> corrupted privilege manager metadata. To reinitialize, do 'initialize 
> authorization, drop' followed by 'initialize authorization'. This deletes and 
> recreates privilege manager metadata. Trafodion metadata is not affected.
> *** ERROR[1234] Authorization need to be reinitialized due to missing or 
> corrupted privilege manager metadata. To reinitialize, do 'initialize 
> authorization, drop' followed by 'initialize authorization'. This deletes and 
> recreates privilege manager metadata. Trafodion metadata is not affected.
> *** ERROR[1234] Authorization need to be reinitialized due to missing or 
> corrupted privilege manager metadata. To reinitialize, do 'initialize 
> authorization, drop' followed by 'initialize authorization'. This deletes and 
> recreates privilege manager metadata. Trafodion metadata is not affected.
> *** ERROR[1028] The schema must be empty.  It contains at least one object 
> COMPONENTS.
> --- SQL operation failed with errors.
> I cannot run - what can I do?
> Until the problem is fixed, here are some workarounds:
> Workaround #1:
> This problem only occurs in a debug build, do a release build and perform 
> "initialize authorization, drop;"
> Workaround #2:
> If you want to continue to run with a debug build, run the following steps:
> swhbase
> create 'TRAFODION._PRIVMGR_MD_.COLUMN_PRIVILEGES', {NAME => '#1'}
> create 'TRAFODION._PRIVMGR_MD_.SCHEMA_PRIVILEGES', {NAME => '#1'}
> quit
> sqlci
> initialize authorization, drop;
> exit;
> swhbase
> disable 'TRAFODION._PRIVMGR_MD_.COLUMN_PRIVILEGES'
> drop 'TRAFODION._PRIVMGR_MD_.COLUMN_PRIVILEGES'
> disable 'TRAFODION._PRIVMGR_MD_.SCHEMA_PRIVILEGES'
> drop 'TRAFODION._PRIVMGR_MD_.SCHEMA_PRIVILEGES'
> exit
> Workaround #3:
> Otherwise, you can drop trafodion -> initialize trafodion, drop;



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to