I have restored a database to a new DSN, when I load it into memory, it applies the redo but then fails with :
21:34:53.53 Err : : 20057: TT14000: TimesTen daemon internal error: Could not send 'manage' request to subdaemon rc -2 err1 703 err2 9999
21:34:53.53 Info: : 20057: daInvalidateDatabase(/u01/data/tt/jd_aggr_store/data); shmKey 17891808, why=Could not send manage request to subdaemon
21:34:53.53 Info: : 20057: Starting daRecovery for 2491
21:34:53.53 Info: : 20057: About to destroy SHM 1890222118
21:34:53.53 Info: : 20057: About to destroy PL/SQL SHM 1890254891
21:34:53.53 Err : : 20057: TT14000: TimesTen daemon internal error: Could not manage data store /u01/data/tt/jd_aggr_store/data as required by policy. Return code 1 Error 703 err2 9999 message 'Failed in connect'
I have checked the articles on MOS but my sem settings don't match the bug listed. Also, I am on 184.108.40.206.1 which is excluded from the bug.
Any suggestions on resolving this?
kernel.shmmax = 1099511627776
kernel.shmall = 4294967296
kernel.shmmni = 4096
kernel.sem = 2048 64000 256 64
vm.nr_hugepages = 268177
How have you restored a database? Could you please provide more information about it?
I'm interested in the following:
1 - Source dab version + DSN settings
2 - How have you restoring the new DSN
3 - ttstatus output
4 - platform (just in case)
Additional thoughts about your problem:
1 - regarding ID 1463458.1, Documentation says about Connection attribute the following:
"0 or no value - Indicates that the default value is used.
The default value is the lesser of 2000 or the number of semaphores specified in the SEMMSL kernel parameter.
An integer from 1 through 2000 -The value represents the maximum number of connections."
In your case, the timesten choose 2000 value (2000 < 2048). Even though the support says that it works in >11.2.2 you can check it easily by adding the Connection attribute in your DSN. Like this Connection=1900
2 - There is some Problems with PLSQL setting, but you didn't mention it, so just in case
PLSQL_MEMORY_ADDRESS - ID 1364564.1
PLSQL_MEMORY_SIZE - ID 12882032.8
3 -waiting the answers on my questions.
I hope this help.