首页 > 其他分享 >DP8.0安装步骤session

DP8.0安装步骤session

时间:2023-02-13 19:57:20浏览次数:57  
标签:00 UX 步骤 HP DP8.0 B.11 session 32 A.08

[root@rx6600]#./omnisetup.sh -CM -IS

The omnisetup.sh script did not complete the last time it was run.
Cell Manager still has to be installed
Installation Server still has to be installed

The omnisetup.sh script can now resume the installation session
or it can ignore the saved state and start a new session.
If you choose to ignore, the script will erase the saved state
and will process only the command line options.
Do you want the setup to resume the installation? (Y/n)
y
Resuming (using the specified CLI options)...

No Data Protector software detected on the target system.

Passed: The user account "hpdp" will be used for the IDB service.
Passed: Port number "7112" will be used for the "hpdp-idb" service.
Passed: Port number "7113" will be used for the "hpdp-idb-cp" service.
Passed: Port number "7116" will be used for the "hpdp-as" service.
Passed: Port number "9999" will be used for the "hpdp-as" service.
Passed: The kernel parameter value: SHMMAX = 2684354560.
The minimum required parameter value is "2684354560".
Passed: There are "8557428736" bytes of available system memory.
8 GB of system memory are recommended.
4 GB of system memory are required.
Passed: Data Protector installation requires 2764800 kilobytes of free
storage space on the "/opt" filesystem.
The filesystem "/opt" has 3420264 kilobytes of free space.
Passwd: Data Protector installation requires 308224 kilobytes of free
storage space on the "/var" filesystem.
The filesystem "/var" has 6104808 kilobytes of free space.
Passed: Data Protector installation requires 6144 kilobytes of free
storage space on the "/" filesystem.
The filesystem "/" has 797296 kilobytes of free space.

Do you wish to start AutoPass installation? (Y/n)
y
Starting AutoPass installation...

======= 02/13/23 19:38:11 MST BEGIN swinstall SESSION
(non-interactive) (jobid=rx6600-0034)

* Session started for user "root@rx6600".

* Beginning Selection
* Target connection succeeded for "rx6600:/".
* Source:
/cdrom/hpux/AUTOPASS/HPOvLic-05.51.061-HPUX11.22_IPF64-release.depot

* Targets: rx6600:/
* Software selections:
HPOVLIC.HPOVLIC,r=5.51.061,a=HP-UX_B.11.23_32/64,v=HP,fr=5.51.061,fa=HP-UX_B.11.23_32/64
HPOVLIC.HPOVLICJ,r=5.51.061,a=HP-UX_B.11.23_32/64,v=HP,fr=1.4.0.0,fa=HP-UX_B.11.23_32/64
* Selection succeeded.


* Beginning Analysis and Execution
* Session selections have been saved in the file
"/.sw/sessions/swinstall.last".
* "rx6600:/": There will be no attempt to mount filesystems
that appear in the filesystem table.
* The execution phase succeeded for "rx6600:/".
* Analysis and Execution succeeded.


NOTE: More information may be found in the agent logfile using the
command "swjob -a log rx6600-0034 @ rx6600:/".

======= 02/13/23 19:38:35 MST END swinstall SESSION (non-interactive)
(jobid=rx6600-0034)


NOTE: AutoPass requires JRE version 1.4.2_08 or higher versions.
NOTE: Please create a link /opt/OV/HPOvLIC/jre to the system's jre directory.
ln -s /opt/OV/HPOvLIC/jre <JRE_INSTALLED_PATH>

AutoPass has been successfully installed

Installing Data Protector A.08.00 Cell Manager and Installation Server...


======= 02/13/23 19:38:35 MST BEGIN swinstall SESSION
(non-interactive) (jobid=rx6600-0035)

* Session started for user "root@rx6600".

* Beginning Selection
* Target connection succeeded for "rx6600:/".
* "rx6600:/cdrom/hpux/DP_DEPOT": Cannot open the logfile on
this target or source. Possibly the media is read-only or
there is a permission problem. Check the daemon logfile and
"/var/tmp/swagent.log" on this host for more information.
* Source: /cdrom/hpux/DP_DEPOT
* Targets: rx6600:/
* Software selections:
+ B6960MA,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP
DATA-PROTECTOR.OMNI-AUTODR-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-CC,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.31_IA
DATA-PROTECTOR.OMNI-CC-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-CF-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-CHS-LS-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-CORE,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.23_IA
DATA-PROTECTOR.OMNI-CORE-IS,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.23_IA
DATA-PROTECTOR.OMNI-CS,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.31_IA
DATA-PROTECTOR.OMNI-DA,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.31_IA
DATA-PROTECTOR.OMNI-DA-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-DB2-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-DOCS,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-DOCS-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-EMC-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-FRA-LS-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-INF-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-INTEG-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-JCE-DISPATCHER,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.31_IA
DATA-PROTECTOR.OMNI-JCE-SERVICEREGISTRY,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.31_IA
DATA-PROTECTOR.OMNI-JPN-LS-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-LOTUS-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-MA,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.31_IA
DATA-PROTECTOR.OMNI-MA-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-NDMP-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-OR8-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-SAP-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-SAPDB-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-SMISA-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-SODA-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-SSEA-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-SYB-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-TS-AS,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.31_IA
DATA-PROTECTOR.OMNI-TS-CF-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-TS-CORE,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.23_IA
DATA-PROTECTOR.OMNI-TS-CS,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.31_IA
DATA-PROTECTOR.OMNI-TS-JRE,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.31_IA
DATA-PROTECTOR.OMNI-TS-PEGASUS-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-VEPA-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-VMW-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-VMWAREGRE-AGENT-P,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.11_32/64
DATA-PROTECTOR.OMNI-WS,r=A.08.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.08.00,fa=HP-UX_B.11.31_IA
* A "+" indicates an automatic selection due to dependency or
the automatic selection of a patch or reference bundle.
* Selection succeeded.


* Beginning Analysis and Execution
* Session selections have been saved in the file
"/.sw/sessions/swinstall.last".
* "rx6600:/": There will be no attempt to mount filesystems
that appear in the filesystem table.
* The execution phase succeeded for "rx6600:/".
* Analysis and Execution succeeded.


NOTE: More information may be found in the agent logfile using the
command "swjob -a log rx6600-0035 @ rx6600:/".

======= 02/13/23 19:59:54 MST END swinstall SESSION (non-interactive)
(jobid=rx6600-0035)


Installation/upgrade session finished.
[root@rx6600]#

 

[root@rx6600]#./omnisv status
ProcName Status [PID]
===============================
crs : Active [10801]
mmd : Active [10799]
kms : Active [10800]
hpdp-idb : Active [10392]
hpdp-idb-cp : Active [10203]
hpdp-as : Active [10833]
omnitrig : Active
Sending of traps disabled.
===============================
Status: All Data Protector processes/services up and running.
[root@rx6600]#./omnidbcheck -extended
Check Level Mode Status
===========================================================
Database connection -connection OK
Schema consistency -schema_consistency OK
Datafiles consistency -verify_db_files OK
Database consistency -database_consistency OK
Media consistency -media_consistency OK
SIBF(readability) -sibf OK
DCBF(presence and size) -bf OK
OMNIDC(consistency) -dc OK
DONE!
[root@rx6600]#./omnisv -version
HP Data Protector A.08.00: OMNISV, internal build 596, built on Sun May 19 14:20:44 2013
[root@rx6600]#

标签:00,UX,步骤,HP,DP8.0,B.11,session,32,A.08
From: https://www.cnblogs.com/rsrzrcj/p/17117577.html

相关文章

  • jstack排查cpu占用高的步骤
    通过jstack排查cpu占用高的问题1.通过top命令找到cpu占用高的应用程序进程2.通过top-H-ppid查看该应用中占用CPU高的线程。3.通过printf"%x\n"pid将线程高的线程......
  • onnxruntime.InferenceSession
      https://vimsky.com/examples/detail/python-method-onnxruntime.InferenceSession.html  https://github.com/htshinichi/caffe-onnx/blob/master/onnxmodel/t......
  • 通过FTP获得靶机Shell步骤说明
    通过FTP获得靶机Shell步骤说明当已经获取到FTP的用户名和密码,并且该用户有权限上传文件以及创建文件,那么基于此获取Shell的步骤如下:1.在KaliLinux上利用ssh-keygen命令......
  • Connect to RDS using shadow session
    1.Findoutcurrentactivesessions.Usingoneofthetwocommandsqwinsta/server:{rds_server}quser/server:{rds_server}RecordsessionID2.Connectmstsc/......
  • cookie、localStorage、sessionStorage的区别
    1.cookie:能存储内容较小,在4k左右,一般用作保存用户登录状态、记住密码,记住账号使用。不清除的话会一直存在,可以设置过期时间自动清除,设置的时候可以设置在不同的域下面。......
  • AD22 PCB导出Gerber文件详细步骤
    PCB绘制好,检查完成后,就可以把文件交给PCB工厂生产了,一般有两种方式:第一种最简单就是直接将PCB文件压缩打包,发给工厂。第二种生成Gerber等相关资料,再压缩打包,发给......
  • 【SpringBoot】Session共享
    本文参考SpringBoot一个依赖搞定session共享,没有比这更简单的方案了!在传统的单服务架构中,只有一个服务器,那就不会存在session共享的问题,但如果在分布式/集群项目......
  • Cookie 和 Session 区别
    Cookie保存客户的数据,服务器产生发回客户端Cookie数据保存客户端,不安全Cookie数据限制64KBCookie保存SessionID值Session数据存储服务器相对Cookie安全不限制类......
  • 09 Cookie与Session组件
    Cookie与Session组件cookie与sessionCookie的由来HTTP协议是无状态的状态可以理解为客户端和服务器在某次会话中产生的数据,那无状态的就是这些数据不会被保留。会话中......
  • Spring+MyBatis整合步骤
    一、两者整合的主要工作:把MyBatis框架中使用到的核心对象(组件)配置到Spring中,交给Spring来创建管理;具体来说:将MyBatis匹配文件中的数据源、SQL映射文件、SqlSessionFactoryBu......