We are using the stored procedure wlm_set_client_info to identify which reports are running on our datawarehouse, we've setup Microstrategy following the guide on the DB2 best practices website:
DB2BP_WLM_Setting_Client_Info_Fields.pdf
This allows us to link the executing sql with a report on the microstrategy level,
facilitating the communication between the Microstrategy administrator and the DBA team,
this works for other multier environments as well, and is very useful in my opinion,
The issue described in the subject occurred when our system engineer was setting up a drp method for our datawarehouse,
during this time our file systems were unmounted and remounted,
after this intervention our microstrategy administrator complained that reports no longer executed and gave the error message when the call to the stored procedure wlm_set_client_info was mad by Microstrategy,
after some investigation we discovered that not only this stored procedure , but ALL stored procedures showed the same error message, SQL1131N
SQL1131N error code in the information center
in the end we discovered that during the system intervention, the system engineer assumed that the fenced user of our db2 instance was not used, so he removed this user,
db2 started and worked correctly except for the stored procedures that were to be executed by the fenced user,
once the fenced user was created again with the correct UID,
the system behaved normally as before.
No comments:
Post a Comment