Di
seguito gli step necessari all'Upgrade del software ODI dalla versione
12.2.1.2.6 alla versione 12.2.1.4.0
STEP |
NOTA |
Creazione
clone macchina DB |
|
Riconfigurazione
/etc/hots |
1.
Configurazione
del file /etc/hosts |
Riconfigurazione
network DB |
1.
Modifica
configurazione listener.ora con nuovo <hostname> 2.
Modifica
configurazione tnsnames.ora con nuovo <hostname> 3.
Avvio
listener |
Startup
DB |
1.
Avvio
istanza di database METAINTA |
Creazione
clone macchina ODI |
|
Riconfigurazione
/etc/hots |
1)Configurazione del file /etc/hosts |
Eseguire
riconfigurazione Repository ODI - Connettersi
al Master Repository SUPERVISOR/Welcome1$ |
1.
Modifica
URL ODI STUDIO Connection Login INFOBOARD_SVIL con nuovo IP 2.
modificare
i puntamenti del workrepository sulla macchina del DB clonato 1.
(Modifica
Topology\Repositories\Work Repositories\WORKREP\JDBC\JDBC URL con nuovo IP) 3.
modificare
i puntamenti dell'agent alla nuova macchina ODI clonata 4.
disabilitare
tutte le schedulazione dell'agent sulla tabella SNP_PLAN_AGENT 1.
Backup
tabella SNP_PLAN_AGENT 2) UPDATE a D : UPDATE
SNP_PLAN_AGENT SET STAT_PLAN = 'D'; |
Riconfigurazione
Dominio WebLogic |
Admin Server URL: http://<hostname_odi_clone>:7001 |
Start
weblogic |
|
Connettersi
alla console di Weblogic e test agent ODI |
1.
https://<hostname_odi_clone>:7001/console 0.
Verificare
che l'Admin sia RUNNING 1.
Start Managed Server di ODI |
Shutdown
di tutti i processi Weblogic |
1)Stop di tutti i processi weblogic chiudendoli dalla console: ·
https://<hostname_odi_clone>:7001/console 2) cd <ODIDOM>/bin ·
./stopNodeManager.sh 3)Verifica
dell'assenza di processi java attivi e riferibili a weblogic: ·
ps -ef | grep
java |
Installazione
software ODI 12.2.1.4.0 |
JDK FMW 12.2.1.4.0 ODI 12.2.1.4.0 |
Verifica
se il Repository può essere upgradato e stop di tutti i processi |
Start the Upgrade
Assistant. (UNIX) ./ua
-readiness
|
Verifica
degli schema presenti |
SET LINE 120 COLUMN
MRC_NAME FORMAT A14 COLUMN
COMP_ID FORMAT A20 COLUMN
VERSION FORMAT A12 COLUMN
STATUS FORMAT A9 COLUMN
UPGRADED FORMAT A8 SELECT
MRC_NAME, COMP_ID, OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY
ORDER BY MRC_NAME, COMP_ID ; |
Inizio
Upgrade ODI alla 12.2.1.4.0 |
Settare i path della versione ODI 12.2.1.4.0 quando ci si collega alla macchina CLONE nel .bash_profile |
Upgrading Product Schemas Using
the Upgrade Assistant |
Start the Upgrade
Assistant. (UNIX) ./ua select Individually
Selected Schemas.
Save Response File |
Verifica
degli schema presenti upgradati |
SET LINE 120 COLUMN
MRC_NAME FORMAT A14 COLUMN
COMP_ID FORMAT A20 COLUMN
VERSION FORMAT A12 COLUMN
STATUS FORMAT A9 COLUMN
UPGRADED FORMAT A8 SELECT
MRC_NAME, COMP_ID, OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY
ORDER BY MRC_NAME, COMP_ID ; OPPURE SELECT
MRC_NAME, COMP_ID, OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY ORDER BY
UPGRADED desc ; |
Backing
Up the Domain |
Domain Location: <ODIDOM> (UNIX) cp -rf
mydomain mydomain_backup cp -rf <ODIDOM>
<ODIDOM_20210630> |
Reconfiguration
Wizard Domain |
Start Reconfig
Assistant (UNIX)
./reconfig.sh -log=<inserire path e
file di log> -log_priority=ALL where -log=log_file
is the absolute path of the log file you'd like to create for the domain reconfiguration session.
This can be helpful if you need to troubleshoot the reconfiguration process. The parameter
-log_priority=ALL ensures that logs are logged in fine mode. The Reconfiguration Progress
screen displays the progress of the reconfiguration process. During this process: • Domain information is
extracted, saved, and updated. • Schemas, scripts, and other
such files that support your Fusion Middleware products are updated. When the progress bar shows
100%, click Next. |
Upgrading
Domain Component Configurations |
Start the Upgrade
Assistant. (UNIX) ./ua Select All
Configurations Used By a Domain. The screen name changes to WebLogic
Components. |
Starting
Servers and Processes |
Domain Location: <ODIDOM> Step 1: Start the
Administration Server: (UNIX)
NEW_DOMAIN_HOME/bin/startWebLogic.sh Step 2: Start Node
Manager (UNIX)
NEW_DOMAIN_HOME/bin/startNodeManager.sh Step 3: Start
eventuali ORACLE Components (UNIX)
NEW_DOMAIN_HOME/bin/startComponent.sh component_name Step 4: Start the
Managed Servers - se necessario (UNIX)NEW_DOMAIN_HOME/bin/startManagedWebLogic.sh
managed_server_name admin_url Eseguire
step 1 e 2 e poi collegarsi alla console per verifica servizi, processi e
start managed server ODI: https://<hostname_odi_clone>:7001/console http://titappocm11lits:7001/console/login/LoginForm.jsp LOG: /u01/data/domains/ODI12INF/INF-ODIDOM_SVIL/servers/ODI_INF_SVIL_1/logs/ODI_INF_SVIL_1.log /u01/data/domains/ODI12INF/INF-ODIDOM_SVIL/servers/ODI_INF_SVIL_1/logs/oracledi/odiagent.log |
|
CHECK domain with line command: cd
/u01/app/oracle/middleware/ODI12214INF/oracle_common/common/bin [oracle@titappocm11lits
bin]$ ./wlst.sh Initializing
WebLogic Scripting Tool (WLST) ... Welcome to WebLogic
Server Administration Scripting Shell Type help() for help
on available commands wls:/offline>
readDomain('/u01/data/domains/ODI12INF/INF-ODIDOM_SVIL') wls:/offline/INF-ODIDOM_SVIL>ls
() drw- AppDeployment drw- CoherenceClusterSystemResource drw- Credential drw- EmbeddedLDAP drw- JDBCSystemResource drw- Keystore drw- Library drw- Machine drw- NMProperties drw- Security drw- SecurityConfiguration drw- Server drw- ServerTemplate drw- ShutdownClass drw- StartupClass drw- StartupGroupConfig drw- WLDFSystemResource -rw- Active false -rw- AdminServerName
AdminODI_INF_SVIL -rw- AdministrationMBeanAuditingEnabled false -rw- AdministrationPort 9002 -rw- AdministrationPortEnabled false -rw- AdministrationProtocol t3s -rw- ArchiveConfigurationCount 0 -rw- AutoDeployForSubmodulesEnabled true -rw- BatchJobsDataSourceJndiName null -rw- BatchJobsExecutorServiceName null -rw- ClusterConstraintsEnabled false -rw- ConfigBackupEnabled false -rw- ConfigurationAuditType null -rw- ConfigurationVersion 12.2.1.4.0 -rw- ConsoleContextPath console -rw- ConsoleEnabled true -rw- ConsoleExtensionDirectory console-ext -rw- DbPassiveMode false -rw- DbPassiveModeGracePeriodSeconds 30 -rw- DiagnosticContextCompatibilityModeEnabled true -rw- DomainVersion 12.2.1.4.0 -rw-
EnableEeCompliantClassloadingForEmbeddedAdaptersfalse -rw- ExalogicOptimizationsEnabled false -rw- Id 0 -rw- InternalAppsDeployOnDemandEnabled true -rw- JavaServiceConsoleEnabled false -rw- JavaServiceEnabled false -rw- LastModificationTime 0 -rw- LogFormatCompatibilityEnabled false -rw- MaxConcurrentLongRunningRequests 50 -rw- MaxConcurrentNewThreads 50 -rw- MsgIdPrefixCompatibilityEnabled true -rw- Name INF-ODIDOM_SVIL -rw- Notes null -rw- OCMEnabled true -rw- ParallelDeployApplicationModules false -rw- ParallelDeployApplications false -rw- PartitionUriSpace /partitions -rw- ProductionModeEnabled false -rw- RootDirectory null -rw- ServerMigrationHistorySize 100 -rw- ServiceMigrationHistorySize 100 -rw- SiteName null -rw- Tag |
CHECK
UPGRADE |
CHECK con connessione ODI tramite ODISTUDIO
versione 12.2.1.4.0 1.
Check OdiAgent |
Nessun commento:
Posta un commento