Organizations collectively automatic proposal considerations during development
[Notes when you add a field to PRGR / PRCL]
① must always be MEGA at the same time as the production migration.
(Beforehand not afford to production shifts to correct only file)
(exception)
when an extension of the field of PCGR / PRCL is, it is possible to production shifts earlier in the LIFE / J than PC.
Not an error because it specifies an explicit field in the INSERT statement in SQL statements when you set the value to PRGR / PRCL of Life / J in the <application host transmission> application. (When extension field is a number items, impossible)
② there is a need to permission settings in the file after the production migration.
In the next morning of production shifts (as much as possible first thing in the morning), and the authority setting of the expanded file.
[Reason]
<application host transmission> application, Life / J of DB (PRGR, PRCL) to access to, are using a user profile that is named # APPUPLDR #.
When you extend the file, # for APPUPLDR * CHANGE authority of grant that have been file to # disappears, there is a need to re-set the authority and
If you do not re-set the permissions at the time was also extended file test environment, Note that it is not possible to upload the proposal data from MEGA.
③ authorization → GRTOBJAUT (PF, there needs to be authorization to each of LF)
đang được dịch, vui lòng đợi..