{"id":5117,"date":"2014-06-11T15:19:49","date_gmt":"2014-06-11T15:19:49","guid":{"rendered":"https:\/\/pitss.org\/us\/?p=5117"},"modified":"2017-05-15T11:24:44","modified_gmt":"2017-05-15T15:24:44","slug":"how-to-load-database-objects-into-pitss-con","status":"publish","type":"post","link":"https:\/\/pitss.org\/us\/2014\/06\/11\/how-to-load-database-objects-into-pitss-con\/","title":{"rendered":"How to Load Database Objects into PITSS.CON"},"content":{"rendered":"<p>When performing a Forms upgrade, an analysis of your application, or modernizing your Forms to ADF using PITSS.CON, the application database objects are necessary when performing such tasks. In order to load them into the PITSS.CON repository, you will need to make sure your PITSS.CON user is assigned the application database schema containing the database objects you need.<\/p>\n<p>Use these steps to set up your PITSS.CON environment for loading database objects:<\/p>\n<p>1. Log into PITSS.CON with the MIG user.<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2014\/06\/image.png\"><img loading=\"lazy\" decoding=\"async\" style=\"margin: 0px;padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" title=\"image\" src=\"https:\/\/pitss.org\/files\/2014\/06\/image_thumb.png\" alt=\"image\" width=\"244\" height=\"142\" border=\"0\" \/><\/a><\/p>\n<p>2. Go to \u201cUser Access\u201d.<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2014\/06\/image1.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" title=\"image\" src=\"https:\/\/pitss.org\/files\/2014\/06\/image_thumb1.png\" alt=\"image\" width=\"510\" height=\"393\" border=\"0\" \/><\/a><\/p>\n<p>3. Expand your group name to find your PITSS.CON user by clicking the \u201c+\u201d button next to the group name. In this example, the PITSS.CON user we want to load database objects into is in the group \u201cUSERS\u201d.<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2014\/06\/image2.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" title=\"image\" src=\"https:\/\/pitss.org\/files\/2014\/06\/image_thumb2.png\" alt=\"image\" width=\"515\" height=\"340\" border=\"0\" \/><\/a><\/p>\n<p>4. Select the PITSS.CON user inside the group. In this example, we are selecting the PITSS1 user. Once this is done, you will notice that the Users table may fill in with different schemas. Once your PITSS.CON user is selected, click \u201cChange Connect String\u201d to update the connect string to your application database.<\/p>\n<p><strong>NOTE: If the PITSS.CON group the PITSS.CON user belongs to has any database objects already loaded, they will need to be removed from the PITSS.CON repository before continuing. Otherwise, you may encounter an error when selecting \u201cChange Connect String\u201d.<\/strong><\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2014\/06\/image3.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" title=\"image\" src=\"https:\/\/pitss.org\/files\/2014\/06\/image_thumb3.png\" alt=\"image\" width=\"517\" height=\"342\" border=\"0\" \/><\/a><\/p>\n<p>5. Enter the username, password, and connect string of your application database userid. In this example, we are using a user called \u201cadmin\u201d. Click \u201cTest Connect String\u201d to save the connect string. <strong>NOTE: Make sure the application database userid you are entering has the \u201cselect on v_$database\u201d grant given to it.<\/strong><\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2014\/06\/image4.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" title=\"image\" src=\"https:\/\/pitss.org\/files\/2014\/06\/image_thumb4.png\" alt=\"image\" width=\"394\" height=\"188\" border=\"0\" \/><\/a><\/p>\n<p>6. Click \u201cOK\u201d when asked if you want to save as the new working database.<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2014\/06\/image5.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" title=\"image\" src=\"https:\/\/pitss.org\/files\/2014\/06\/image_thumb5.png\" alt=\"image\" width=\"390\" height=\"162\" border=\"0\" \/><\/a><\/p>\n<p>7. The Application Connection field will be updated with the specified userid. In the Users table, you should see a list of all available schemas on the application database. For the schema you wish to assign the PITSS.CON user to, select the row with that schema and select the \u201cAssign a PITSS.CON User\u201d button. In this example, we are assigning the PITSS1 user to the WEBUTIL schema.<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2014\/06\/image6.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" title=\"image\" src=\"https:\/\/pitss.org\/files\/2014\/06\/image_thumb6.png\" alt=\"image\" width=\"513\" height=\"342\" border=\"0\" \/><\/a><\/p>\n<p>8. Select the PITSS.CON user you wish to assign to the schema and click OK.<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2014\/06\/image7.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" title=\"image\" src=\"https:\/\/pitss.org\/files\/2014\/06\/image_thumb7.png\" alt=\"image\" width=\"343\" height=\"318\" border=\"0\" \/><\/a><\/p>\n<p>9. You will see that the PITSS.CON user is assigned to the application schema. Repeat steps 7-8 for as many schemas as needed.<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2014\/06\/image8.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" title=\"image\" src=\"https:\/\/pitss.org\/files\/2014\/06\/image_thumb8.png\" alt=\"image\" width=\"508\" height=\"336\" border=\"0\" \/><\/a><\/p>\n<p>10. Log out of the MIG user and log into your PITSS.CON user.<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2014\/06\/image9.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" title=\"image\" src=\"https:\/\/pitss.org\/files\/2014\/06\/image_thumb9.png\" alt=\"image\" width=\"340\" height=\"199\" border=\"0\" \/><\/a><\/p>\n<p>11. Go to Administration \u2013&gt; Settings.<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2014\/06\/image10.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" title=\"image\" src=\"https:\/\/pitss.org\/files\/2014\/06\/image_thumb10.png\" alt=\"image\" width=\"500\" height=\"386\" border=\"0\" \/><\/a><\/p>\n<p>12. Scroll down to \u201cConnection String to Application Database\u201d and select it. You will need to provide the same application database connect string in these fields as you did in the MIG user. Click \u201cTest Connect String\u201d to save the changes.<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2014\/06\/image11.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" title=\"image\" src=\"https:\/\/pitss.org\/files\/2014\/06\/image_thumb11.png\" alt=\"image\" width=\"497\" height=\"329\" border=\"0\" \/><\/a><\/p>\n<p>13. If successful, you should see a message at the bottom saying, \u201cThe connection string is correct.\u201d<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2014\/06\/image12.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" title=\"image\" src=\"https:\/\/pitss.org\/files\/2014\/06\/image_thumb12.png\" alt=\"image\" width=\"498\" height=\"43\" border=\"0\" \/><\/a><\/p>\n<p>14. Click the \u201cExit\u201d button to return to the main menu. Go to Maintenance \u2013&gt; DB Handling.<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2014\/06\/image13.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" title=\"image\" src=\"https:\/\/pitss.org\/files\/2014\/06\/image_thumb13.png\" alt=\"image\" width=\"496\" height=\"381\" border=\"0\" \/><\/a><\/p>\n<p>15. Click \u201cLoad\u201d to start the loading procedure for loading the database objects.<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2014\/06\/image14.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" title=\"image\" src=\"https:\/\/pitss.org\/files\/2014\/06\/image_thumb14.png\" alt=\"image\" width=\"505\" height=\"334\" border=\"0\" \/><\/a><\/p>\n<p>16. The \u201cSelect Database Objects\u201d table will appear. All schemas assigned to your PITSS.CON user will appear here. For the schema objects you wish to load, please place a check mark next to each schema and specify a password for each schema. When ready, click \u201cLoad\u201d again to load the database objects into PITSS.CON.<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2014\/06\/image15.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" title=\"image\" src=\"https:\/\/pitss.org\/files\/2014\/06\/image_thumb15.png\" alt=\"image\" width=\"511\" height=\"338\" border=\"0\" \/><\/a><\/p>\n<p>This will allow you to load database objects into PITSS.CON.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When performing a Forms upgrade, an analysis of your application, or modernizing your Forms to ADF using PITSS.CON, the application database objects are necessary when performing such tasks. In order to load them into the PITSS.CON repository, you will need to make sure your PITSS.CON user is assigned the application database schema containing the database [&hellip;]<\/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":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[4,6,10],"tags":[41,25,3,27,7],"class_list":["post-5117","post","type-post","status-publish","format-standard","hentry","category-install-config","category-pitss-con","category-windows","tag-configuration","tag-customer-support-request","tag-faq","tag-oracle-database","tag-pitss-con"],"_links":{"self":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts\/5117","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=5117"}],"version-history":[{"count":3,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts\/5117\/revisions"}],"predecessor-version":[{"id":9091,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts\/5117\/revisions\/9091"}],"wp:attachment":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/media?parent=5117"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/categories?post=5117"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/tags?post=5117"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}