VS_KEY in Tbl_Resource_Pool Configuration
(Doc ID 1909166.1)
Last updated on AUGUST 31, 2020
Applies to:
Oracle Communications ASAP - Version 4.7.1 and laterInformation in this document applies to any platform.
Goal
We found in the resource_pool.ins file, for inserting data into tbl_resource_pool, that all the NE’s last parameters are passed as a 0 as shown below for LDAP.
exec :retval := SSP_new_resource ( 'PROD', 'LDAP_P', 'dev01_LDAP', 'W', 0);
exec :retval := SSP_new_resource ( 'PROD', 'LDAP_P', 'dev02_LDAP', 'W', 0);
exec :retval := SSP_new_resource ( 'PROD', 'LDAP_P', 'dev03_LDAP', 'W', 0);
exec :retval := SSP_new_resource ( 'PROD', 'LDAP_P', 'dev04_LDAP', 'W', 0);
However only for XXXXXX, it is showing 1 from second port onward.
exec :retval := SSP_new_resource ( 'PROD','XXXXXX_P','XXXXXX#1','G','0');
exec :retval := SSP_new_resource ( 'PROD','XXXXXX_P','XXXXXX#2','G','1');
exec :retval := SSP_new_resource ( 'PROD','XXXXXX_P','XXXXXX#3','G','1');
exec :retval := SSP_new_resource ( 'PROD','XXXXXX_P','XXXXXX#4','G','1');
exec :retval := SSP_new_resource ( 'PROD','XXXXXX_P','XXXXXX#5','G','1');
We are not sure why the set up is like this? Is it good practice to keep 0 or 1. If 1 is not good to keep, then what will be the impact.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |