Search
- Filter Results
- Location
- Classification
- Include attachments
- https://knowledge.exlibrisgroup.com/Aleph/Knowledge_Articles/Run_Upgrade_Express_%22Export_Customer_Data%22_under_TWO_TASKOn the Source Application server, following the steps in the run the "Upgrading 20-23 -UE.ACTUAL RUN" (or similar) document, run the: NOTE: You must be logged in as the appropriate Oracle user for the...On the Source Application server, following the steps in the run the "Upgrading 20-23 -UE.ACTUAL RUN" (or similar) document, run the: NOTE: You must be logged in as the appropriate Oracle user for the database server: in the case of the export from the Source (database) server, that's the Aleph 20 Oracle user; in the case of the import to the Target (database) server, it's the Aleph 23 Oracle user.
- https://knowledge.exlibrisgroup.com/Aleph/Knowledge_Articles/Upgrade_Express%3A_%22DBI_connect(...)%3A_need_explicit_attach_before_authenticating_a_user%22Case 2: Incorrect value for $ORA_HOST in $alephe_root/aleph_start which, in turn, incorrectly set $aleph_db, which caused problems with the perl DBI connection (used by the UE and its environment_chec...Case 2: Incorrect value for $ORA_HOST in $alephe_root/aleph_start which, in turn, incorrectly set $aleph_db, which caused problems with the perl DBI connection (used by the UE and its environment_check script). Case 3: The FQDN of the database host (aka THE host) wasn't entered in the AIK when setting up the server. Commented out the line 'SECURE_REGISTER_LISTENER = (IPC)' at the end of listener.ora - which we believe it is obsolete, and was interfering with Oracle registering with the listener.
- https://knowledge.exlibrisgroup.com/Aleph/Knowledge_Articles/Aleph_Upgrade_ProcessIf it is desired that Ex Libris should perform the upgrade, please fill out the document "Request for Aleph Upgrade by Ex Libris" attached ,@api,deki,files,61722,Request_for_Aleph_Installation_Form.do...If it is desired that Ex Libris should perform the upgrade, please fill out the document "Request for Aleph Upgrade by Ex Libris" attached ,@api,deki,files,61722,Request_for_Aleph_Installation_Form.doc . (Note that the Aleph Installation and Aleph Upgrade Express steps are separate: a site might contract with Ex Libris for the Installation, but run the Upgrade Express themselves.)
- https://knowledge.exlibrisgroup.com/Aleph/Knowledge_Articles/Upgrade_Express_%22Install_Customer_Data%22_process_hangs%3B_hundreds_of_z39_processes_generated%3B_extreme_server_slownessThus, it seems that, when "ALEPH_ADMIN"."SYS_IMPORT_SCHEMA_01" successfully completed and the "/bin/gzip $file" was started, some other things happened in the system – such as a loop in which z39_serv...Thus, it seems that, when "ALEPH_ADMIN"."SYS_IMPORT_SCHEMA_01" successfully completed and the "/bin/gzip $file" was started, some other things happened in the system – such as a loop in which z39_server and z39_gate processes were repeatedly started (This makes no sense, but that does seem to be what is happening.)
- https://knowledge.exlibrisgroup.com/Aleph/Knowledge_Articles/Upgrade_Express_rerun%3A_drop_existing_Oracle_data%3FArticle Type: Q&A Product: Aleph Product Version: 21 Question For a rerun of Upgrade Express, is it necessary to drop the existing Oracle tables on the new server which will be replaced with the fresh...Article Type: Q&A Product: Aleph Product Version: 21 Question For a rerun of Upgrade Express, is it necessary to drop the existing Oracle tables on the new server which will be replaced with the fresh copy? Answer The install_customer_data proc does a clear_ora_user for each user (library), which drops all of the library's existing data. Category: Installation & Upgrades Subject: Upgrade Express Article last edited: 1/21/2014
- https://knowledge.exlibrisgroup.com/Aleph/Knowledge_Articles/Upgrade_Express_Create_Customer_Data_step_stalls_at_very_beginningxxx_user 8184 1 0 Feb10 ? 00:00:00 csh -f /exlibris/aleph/upgrade_express_2201_2301/util/oracle_exp_aleph_libs xxx00 xxx01 xxx10 xxx40 xxx50 xxx60 yes /exlibris/aleph/upgrade_express_2201_2301/logs/lo...xxx_user 8184 1 0 Feb10 ? 00:00:00 csh -f /exlibris/aleph/upgrade_express_2201_2301/util/oracle_exp_aleph_libs xxx00 xxx01 xxx10 xxx40 xxx50 xxx60 yes /exlibris/aleph/upgrade_express_2201_2301/logs/log/create_customer_data.log both DP xxx_user 8232 8184 0 Feb10 ? 00:00:00 csh -f ./util/oracle_exp_aleph_libs_a xxx00 xxx01 xxx10 xxx40 xxx50 xxx60 yes /exlibris/aleph/upgrade_express_2201_2301/logs/log/create_customer_data.log both DP xxx_user 10783 8232 0 Feb10 ? 00:00:00 csh -f util/oracle_expdp_…
- https://knowledge.exlibrisgroup.com/Aleph/Knowledge_Articles/error_lngcirc_status_holding_error_8016Problem Symptoms: While upgrading from Aleph 21 to Aleph 22, the report for the local error files gives the warning: circ_status_holding Significant differences Merge the file in alephe Message 8016 [...Problem Symptoms: While upgrading from Aleph 21 to Aleph 22, the report for the local error files gives the warning: circ_status_holding Significant differences Merge the file in alephe Message 8016 [From Aleph 18, rpc 252, April 2007] is no longer present in Aleph 22 8016 0000 L Ready for transit This change is not documented Cause: Configuration Resolution: Remove the line 8016 0000 L Ready for transit from the local error file at $alephe_root/error_lng/circ_status_holding