Init Block

Jaymie

Hello, I hope everyone is doing well, and thank you for the assistance I received last time. I know resorting to restoring the backup isn't ideal, but I have no other option now. To provide some context on the issue, we have a variable in RDP named 'OAC_LOGIN_INITBLOCK', which contains the following code:
INSERT INTO OAC_LOGIN (USERNAME, LOGIN_TIME, LOGIN_DATE) VALUES (':USER', SYSDATE, TRUNC(SYSDATE));

This code used to function without any issues(Before). However, recently, it started throwing an error on Oracle BI, I was working fine last April 12, but now this is the error:

Error during query processing (SQLDriverConnectW).
Error Details:
Error Codes: OPR4ONWY:U9IM8TAC:U9IM8TAC:U9IM8TAC
State: 08004. Code: 10018. [NQODBC] [SQL_STATE: 08004] [nQSError: 10018] Access for the requested connection is refused. (08004)
State: HY000. Code: 43275. [nQSError: 43275] Message returned from OBIS [ecid:8f23c4ae-d266-45cd-9a0d-ebc0f8444719-00170b6a,0:1:2:6 ts:2024-04-20T20:02:00.312+00:00]. (HY000)
State: HY000. Code: 13024. [nQSError: 13024] Successful completion of init block 'OAC_LOGIN_INITBLOCK' is required. (HY000)

My question is, why did the previously functional code suddenly start causing errors when it worked fine before? Someone told me that insert is not supported on the init block, but why was it working before w/o a problem?

[Deleted User]

It's a question of sequential execution and "required" checkmarks. If your init block 'OAC_LOGIN_INITBLOCK' is marked as "required for authentication" or is sequentially before an init block which is marked as required then any failure of the init block 'OAC_LOGIN_INITBLOCK' will stop execution.

You have to find the root cause for why 'OAC_LOGIN_INITBLOCK' fails. Check the detailed logs which are written upon login of a user.

Also it's best if you take a piece of paper and draw the execution process of what starts when why in order for you to understand questions like execution precedence and sequential dependencies.