- \n
![\"VC_3\"](\"https:\/\/pitss.org\/us\/wp-content\/uploads\/sites\/4\/2017\/03\/VC_3.png\")
<\/a><\/li>\n<\/ul>\n<\/li>\n- In the copied file, replace “&NEW_USER” with your Version Control user (e.g. “VC”). Save and close the file.\n
- \n
![\"VC_4\"](\"https:\/\/pitss.org\/us\/wp-content\/uploads\/sites\/4\/2017\/03\/VC_4.png\")
<\/a><\/li>\n<\/ul>\n<\/li>\n- Open up Command Prompt, and navigate to the folder with the updated script.\n
- \n
![\"VC_5\"](\"https:\/\/pitss.org\/us\/wp-content\/uploads\/sites\/4\/2017\/03\/VC_5.png\")
<\/a><\/li>\n<\/ul>\n<\/li>\n- Launch SQLPLUS with the MIG user and run the script.\n
- \n
![\"VC_6\"](\"https:\/\/pitss.org\/us\/wp-content\/uploads\/sites\/4\/2017\/03\/VC_6.png\")
<\/a><\/li>\n<\/ul>\n<\/li>\n- Log out of SQLPLUS and navigate to the “script_vc” folder located inside the “version_control” folder in the PITSS.CON setup folder.\n
- \n
![\"VC_7\"](\"https:\/\/pitss.org\/us\/wp-content\/uploads\/sites\/4\/2017\/03\/VC_7.png\")
<\/a><\/li>\n<\/ul>\n<\/li>\n- Log into SQLPLUS with the Version Control user and run the script “pitsscon.sql”.\n
- \n
![\"VC_8\"](\"https:\/\/pitss.org\/us\/wp-content\/uploads\/sites\/4\/2017\/03\/VC_8.png\")
<\/a><\/li>\n<\/ul>\n<\/li>\n- When asked to type in the setup folder path, type in the directory where Version Control was installed and press “Enter” (e.g. C:\\pitsscon\\vc).\n
- \n
![\"VC_9\"](\"https:\/\/pitss.org\/us\/wp-content\/uploads\/sites\/4\/2017\/03\/VC_9.png\")
<\/a><\/li>\n<\/ul>\n<\/li>\n- If you see the error, “ORA-02291: integrity constraint (MIG.SELF_REF) violated – parent key not found”, run the following SQL commands with the Version Control use\n
- \n
- INSERT INTO “MIG”.”PITSS_CON” (ID_TOOL, NAME_TOOL, DESC_TOOL, TYPE_TOOL, COLOR) VALUES (’80’, ‘Source Control’, ‘Application and Development Process Management’, ‘FOLDER’, ‘r56g120b184’);<\/li>\n
- INSERT INTO “MIG”.”PITSS_CON” (ID_TOOL, NAME_TOOL, DESC_TOOL, TYPE_TOOL, PARENT_ID, FORM_ASOC, ICON) VALUES (‘8010’, ‘Source Control’, ‘Secure, version and track changes to application files and Oracle DB objects.’, ‘TOOL’, ’80’, ‘vers_control’, ‘vc_add_files_wb’);<\/li>\n
- commit;<\/li>\n
![\"VC_10\"](\"https:\/\/pitss.org\/us\/wp-content\/uploads\/sites\/4\/2017\/03\/VC_10.png\")
<\/a><\/li>\n<\/ul>\n<\/li>\n- In the PITSS.CON database, query the MIG_PITSSCON_USERS table, and look up (and write down) the USER_ID attributes of all installed PITSS.CON users except for MIG.\n
- \n
![\"VC_11\"](\"https:\/\/pitss.org\/us\/wp-content\/uploads\/sites\/4\/2017\/03\/VC_11.png\")
<\/a><\/li>\n<\/ul>\n<\/li>\n- Return to your SQLPLUS session (as the Version Control user) and run the following command for each PITSS.CON user other than MIG. The <USER_ID> attribute should be the value of the attribute for the PITSS.CON user you are updating.\n
- \n
- INSERT INTO “MIG”.”PITSSCON_USERS_RIGHTS” (USER_ID, TOOL_ID, IS_SELECTED) VALUES (‘<USER_ID>’, ‘8010’, ‘Y’);<\/li>\n
![\"VC_12\"](\"https:\/\/pitss.org\/us\/wp-content\/uploads\/sites\/4\/2017\/03\/VC_12.png\")
<\/a><\/li>\n<\/ul>\n<\/li>\n- Commit all changes: commit;\n
- \n
![\"VC_13\"](\"https:\/\/pitss.org\/us\/wp-content\/uploads\/sites\/4\/2017\/03\/VC_13.png\")
<\/a><\/li>\n<\/ul>\n<\/li>\n<\/ol>\nAfter making the above changes, the Source Control button should be available again in PITSS.CON.<\/p>\n
![\"VC_14\"](\"https:\/\/pitss.org\/us\/wp-content\/uploads\/sites\/4\/2017\/03\/VC_14.png\")
<\/a><\/p>\nNOTE: For Forms 12c, when you enter Source Control, and you notice that you are unable to log into your Source Control user other than Administrator, there might have been a corruption when upgrading previously to 16.1 or 16.2.1. A full reinstall of PITSS.CON including the MIG user may be required. Please contact PITSS Support at us.support@pitss.org<\/a> for instructions on how to reinstall MIG and preserve your PITSS.CON license. This particular issue has currently not been seen when upgrading from PITSS.CON 15.4.2 or older to 16.2.2.
\n[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row custom_padding=”0px||0px|” custom_margin=”30px||0px|” background_position_1=”top_left” background_repeat_1=”no-repeat” _builder_version=”3.0.51″][et_pb_column type=”4_4″ _builder_version=”3.0.47″ parallax=”off” parallax_method=”on” background_position=”top_left” background_repeat=”no-repeat”][et_pb_cta title=”Need more information on PITSS.CON? ” button_url=”https:\/\/pitss.org\/products\/pitss-con” button_text=”CODE ANALYSIS TOOL” background_color=”#222222″ _builder_version=”3.0.52″ text_orientation=”left” custom_padding=”45px|50px|45px|50px” custom_button=”on” button_font=”Abel|||on|” border_style=”solid”]Have questions about what PITSS.CON can do? Learn more about the tool’s capabilities at our site.
\n[\/et_pb_cta][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"There is a known issue in PITSS.CON where reinstalling Source Control (also referred to as Version Control) causes Source Control to no longer appear as an option within PITSS.CON. This has been seen after you have upgraded from an older release to either 16.1 or 16.2.1. Users who upgrade from 15.4.2 or older to 16.2.2 […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"
There is a known issue in PITSS.CON where reinstalling Source Control (also referred to as Version Control) causes Source Control to no longer appear as an option within PITSS.CON. This has been seen after you have upgraded from an older release to either 16.1 or 16.2.1. Users who upgrade from 15.4.2 or older to 16.2.2 (or users who are using 15.4.2 or older) will not experience the problem. This is only encountered after an upgrade and Source Control is reinstalled (not upgraded). Fixing the problem will require several steps to restore Source Control functionality in PITSS.CON.<\/p>
- Upgrade your PITSS.CON (all users) to version 16.2.2. Do not worry about the Version Control user as we will reinstall it again.<\/li>
- Once all users are upgraded to PITSS.CON 16.2.2, install Version Control again.<\/li>
- In the PITSS.CON 16.2.2 installer, go into the \"script_install\" folder and locate the script, user_grants.sql<\/strong>. Create a copy of the script and open it in Notepad.
- <\/a><\/li><\/ul><\/li>
- In the copied file, replace \"&NEW_USER\" with your Version Control user (e.g. \"VC\"). Save and close the file.
- <\/a><\/li><\/ul><\/li>
- Open up Command Prompt, and navigate to the folder with the updated script.
- <\/a><\/li><\/ul><\/li>
- Launch SQLPLUS with the MIG user and run the script.
- <\/a><\/li><\/ul><\/li>
- Log out of SQLPLUS and navigate to the \"script_vc\" folder located inside the \"version_control\" folder in the PITSS.CON setup folder.
- <\/a><\/li><\/ul><\/li>
- Log into SQLPLUS with the Version Control user and run the script \"pitsscon.sql\".
- <\/a><\/li><\/ul><\/li>
- When asked to type in the setup folder path, type in the directory where Version Control was installed and press \"Enter\" (e.g. C:\\pitsscon\\vc).
- <\/a><\/li><\/ul><\/li>
- If you see the error, \"ORA-02291: integrity constraint (MIG.SELF_REF) violated - parent key not found\", run the following SQL commands with the Version Control use
- INSERT INTO \"MIG\".\"PITSS_CON\" (ID_TOOL, NAME_TOOL, DESC_TOOL, TYPE_TOOL, COLOR) VALUES ('80', 'Source Control', 'Application and Development Process Management', 'FOLDER', 'r56g120b184');<\/li>
- INSERT INTO \"MIG\".\"PITSS_CON\" (ID_TOOL, NAME_TOOL, DESC_TOOL, TYPE_TOOL, PARENT_ID, FORM_ASOC, ICON) VALUES ('8010', 'Source Control', 'Secure, version and track changes to application files and Oracle DB objects.', 'TOOL', '80', 'vers_control', 'vc_add_files_wb');<\/li>
- commit;<\/li>
- <\/a><\/li><\/ul><\/li>
- In the PITSS.CON database, query the MIG_PITSSCON_USERS table, and look up (and write down) the USER_ID attributes of all installed PITSS.CON users except for MIG.
- <\/a><\/li><\/ul><\/li>
- Return to your SQLPLUS session (as the Version Control user) and run the following command for each PITSS.CON user other than MIG. The <USER_ID> attribute should be the value of the attribute for the PITSS.CON user you are updating.
- INSERT INTO \"MIG\".\"PITSSCON_USERS_RIGHTS\" (USER_ID, TOOL_ID, IS_SELECTED) VALUES ('<USER_ID>', '8010', 'Y');<\/li>
- <\/a><\/li><\/ul><\/li>
- Commit all changes: commit;
- <\/a><\/li><\/ul><\/li><\/ol>
After making the above changes, the Source Control button should be available again in PITSS.CON.<\/p>
<\/a><\/p>NOTE: For Forms 12c, when you enter Source Control, and you notice that you are unable to log into your Source Control user other than Administrator, there might have been a corruption when upgrading previously to 16.1 or 16.2.1. A full reinstall of PITSS.CON including the MIG user may be required. Please contact PITSS Support at us.support@pitss.org<\/a> for instructions on how to reinstall MIG and preserve your PITSS.CON license. This particular issue has currently not been seen when upgrading from PITSS.CON 15.4.2 or older to 16.2.2.<\/p>","_et_gb_content_width":"","footnotes":""},"categories":[6,14],"tags":[11,16,89,12,7,18],"class_list":["post-8779","post","type-post","status-publish","format-standard","hentry","category-pitss-con","category-resolve-issues","tag-11g","tag-11gr2","tag-12c","tag-error","tag-pitss-con","tag-source-control"],"_links":{"self":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts\/8779","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/comments?post=8779"}],"version-history":[{"count":9,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts\/8779\/revisions"}],"predecessor-version":[{"id":11123,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts\/8779\/revisions\/11123"}],"wp:attachment":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/media?parent=8779"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/categories?post=8779"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/tags?post=8779"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Commit all changes: commit;
- Return to your SQLPLUS session (as the Version Control user) and run the following command for each PITSS.CON user other than MIG. The <USER_ID> attribute should be the value of the attribute for the PITSS.CON user you are updating.
- In the PITSS.CON database, query the MIG_PITSSCON_USERS table, and look up (and write down) the USER_ID attributes of all installed PITSS.CON users except for MIG.
- If you see the error, \"ORA-02291: integrity constraint (MIG.SELF_REF) violated - parent key not found\", run the following SQL commands with the Version Control use
- When asked to type in the setup folder path, type in the directory where Version Control was installed and press \"Enter\" (e.g. C:\\pitsscon\\vc).
- Log into SQLPLUS with the Version Control user and run the script \"pitsscon.sql\".
- Log out of SQLPLUS and navigate to the \"script_vc\" folder located inside the \"version_control\" folder in the PITSS.CON setup folder.
- Launch SQLPLUS with the MIG user and run the script.
- Open up Command Prompt, and navigate to the folder with the updated script.
- In the copied file, replace \"&NEW_USER\" with your Version Control user (e.g. \"VC\"). Save and close the file.
- Commit all changes: commit;\n
- Return to your SQLPLUS session (as the Version Control user) and run the following command for each PITSS.CON user other than MIG. The <USER_ID> attribute should be the value of the attribute for the PITSS.CON user you are updating.\n
- In the PITSS.CON database, query the MIG_PITSSCON_USERS table, and look up (and write down) the USER_ID attributes of all installed PITSS.CON users except for MIG.\n
- If you see the error, “ORA-02291: integrity constraint (MIG.SELF_REF) violated – parent key not found”, run the following SQL commands with the Version Control use\n
- When asked to type in the setup folder path, type in the directory where Version Control was installed and press “Enter” (e.g. C:\\pitsscon\\vc).\n
- Log into SQLPLUS with the Version Control user and run the script “pitsscon.sql”.\n
- Log out of SQLPLUS and navigate to the “script_vc” folder located inside the “version_control” folder in the PITSS.CON setup folder.\n
- Launch SQLPLUS with the MIG user and run the script.\n
- Open up Command Prompt, and navigate to the folder with the updated script.\n
- In the copied file, replace “&NEW_USER” with your Version Control user (e.g. “VC”). Save and close the file.\n