Backup may fail with this error :
[61:4001] Error accessing the database, in line 1909, file /svnstore/unix/panther/dp_907_rel_nightly/src/sm/bsm2/bcsmutil.c.
Database subsystem reports:
"Internal error: DbaXXXX functions."
GUI may fail with DbaXXXX error accessing devices & media or related tasks
Justification :
In the pg_log/* files, one or several of similar lines woud appear :
=================================================
2016-09-26 09:00:15 CEST WARNING: out of shared memory
2016-09-26 09:00:15 CEST ERROR: out of shared memory
2016-09-26 09:00:15 CEST HINT: You might need to increase max_locks_per_transaction.
=================================================
Recommendations :
In the postgresql.conf file, the default limit for max_locks_per_transaction = 64.
A review by the CPE IDB / Postgres team shows that this is not adequate to the DP demand and so both Proactive and Reactive recommendation is to increase this value.
Small environments :
max_locks_per_transaction = 1024
Medium size and large environments :
max_locks_per_transaction = 4096
NOTE :
max_locks_per_transaction = 1024 will occupy additional 28MB of memory
max_locks_per_transaction = 4096 will occupy additional 111MB of memory
- comparing to default 64 (if max_connections = 100)
If you unsure, better set the 4069, it just occupies some additional memory
IMPORTANT NOTE : Make a copy of postgresql.conf before you make any changes to it
If this parameter is not set in postgresql.conf (or it is commented out with #), just add the above line to the end on postgresql.conf file.
If this parameter is already set, then make sure it set at least to the above recommended value, if not, change to recommended value.
The config fle is located under following directory (default) of your CM:
WINDOWS : \ProgramData\OmniBack\server\db80\pg\postgresql.conf
UNIX : /var/opt/omni/server/db80/pg/postgresql.conf
This parameter will only became active on the DP services restart.