oracle 部署报错,微软云azure部署oracle报错:PMON (ospid: 7504): terminating the instance due to error 822...

oracle11g启动报错,startup nomount失败,后台alert报错日志如下:

[oracle@pldb1 dbs]$ more /oracle/app/oracle/diag/rdbms/pdunq/powerdes/trace/alert_powerdes.log

Wed Feb 03 20:56:28 2016

Starting ORACLE instance (normal)

....

dispatchers = "(PROTOCOL=TCP) (SERVICE=powerdesXDB)"

audit_file_dest = "/oracle/app/oracle/admin/powerdes/adump"

audit_trail = "DB"

db_name = "powerdes"

db_unique_name = "pdunq"

open_cursors = 300

diagnostic_dest = "/oracle/app/oracle"

Wed Feb 03 20:57:07 2016

PMON started with pid=2, OS id=7504

Wed Feb 03 20:57:07 2016

VKTM started with pid=3, OS id=7506

VKTM running at (100ms) precision

Wed Feb 03 20:57:07 2016

GEN0 started with pid=4, OS id=7510

Wed Feb 03 20:57:07 2016

DIAG started with pid=5, OS id=7512

Wed Feb 03 20:57:07 2016

DBRM started with pid=6, OS id=7514

Wed Feb 03 20:57:07 2016

PSP0 started with pid=7, OS id=7516

Wed Feb 03 20:57:07 2016

DIA0 started with pid=8, OS id=7518

Wed Feb 03 20:57:07 2016

MMAN started with pid=9, OS id=7520

Wed Feb 03 20:57:07 2016

DBW0 started with pid=10, OS id=7522

Wed Feb 03 20:57:07 2016

LGWR started with pid=11, OS id=7524

Wed Feb 03 20:57:07 2016

CKPT started with pid=12, OS id=7526

Wed Feb 03 20:57:07 2016

SMON started with pid=13, OS id=7528

Wed Feb 03 20:57:07 2016

RECO started with pid=14, OS id=7530

Wed Feb 03 20:57:07 2016

MMON started with pid=15, OS id=7532

starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...

Wed Feb 03 20:57:07 2016

MMNL started with pid=16, OS id=7534

starting up 1 shared server(s) ...

ORACLE_BASE from environment = /oracle/app/oracle

PMON (ospid: 7504): terminating the instance due to error 822

Instance terminated by PMON, pid = 7504

[oracle@pldb1 dbs]$

这个极大可能是参数文件出故障了,直接找到原来备份的参数文件,然后启动:

SQL> startup pfile='/oracle/pfile.01' nomount

ORACLE instance started.

Total System Global Area 1453092864 bytes

Fixed Size 2213416 bytes

Variable Size 855640536 bytes

Database Buffers 587202560 bytes

Redo Buffers 8036352 bytes

SQL>

SQL> show parameter spfile

NAME TYPE VALUE

------------------------------------ ----------- ------------------------------

spfile string

SQL> create spfile from pfile='/oracle/pfile.01';

File created.

SQL>

SQL> shutdown immediate

ORA-01507: database not mounted

ORACLE instance shut down.

SQL> startup nomount

ORACLE instance started.

Total System Global Area 1453092864 bytes

Fixed Size 2213416 bytes

Variable Size 855640536 bytes

Database Buffers 587202560 bytes

Redo Buffers 8036352 bytes

SQL>

SQL>

SQL> exit

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

[oracle@pldb1 dbs]$

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Elasticsearch是一个开源的分布式搜索和分析引擎,用于处理大规模数据的实时搜索和分析。Kubernetes(简称K8S)是一个用于自动化部署、扩展和管理容器化应用程序的开源平台。 要在Kubernetes上部署Elasticsearch 8.x集群,可以按照以下步骤进行操作: 1. 创建Kubernetes集群:首先,需要在Kubernetes上创建一个可用的集群。可以使用服务提供商(如AWS、Azure、GCP)或自己搭建的Kubernetes集群。 2. 安装Elasticsearch Operator:Elasticsearch Operator是一个Kubernetes控制器,用于管理Elasticsearch集群的生命周期。可以通过在Kubernetes上安装Elasticsearch Operator来简化集群的管理。 3. 创建Elasticsearch集群配置:使用Elasticsearch Operator创建一个Elasticsearch集群配置文件。配置文件中包含了集群的规模、存储需求、网络设置等信息。 4. 部署Elasticsearch集群:使用kubectl命令或Kubernetes Dashboard将Elasticsearch集群配置文件部署到Kubernetes集群中。Kubernetes会自动创建和管理Elasticsearch节点的Pod。 5. 配置Elasticsearch集群:根据需求,可以配置Elasticsearch集群的参数,如节点数量、副本数、内存和存储资源等。 6. 监控和日志收集:为了监控和管理Elasticsearch集群,可以使用Kubernetes提供的监控和日志收集工具,如Prometheus、Grafana和Elasticsearch自带的监控插件。 7. 高可用性和扩展性:为了实现高可用性和扩展性,可以使用Kubernetes的特性,如水平扩展、自动伸缩和故障转移等。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值