用户不能登录,求救,急!!!!

[复制链接]
查看11 | 回复9 | 2014-9-12 22:37:43 | 显示全部楼层 |阅读模式
我的oracle10g数据库,安装在radhat linux上,以前一直用的好好的,今天因为做个sql操作,需要时间特别长,等不及,就把服务器重新启动了,使用 shutdown abort停掉数据库,reboot计算机,然后发现数据库使用普通用户不能登陆了,输入用户名 密码后一直没有反应,在服务器上也一样,但是使用 connect /as sysdba可以登录,connect system/密码@连接也可以,就是普通用户没有反应,新建一个用户也不能登陆,情况一样。
web管理页面也打不开
在服务器上输入emctl start dbconsole 好长时间才显示成功,但是web页面http://地址:5500/em也打不开
以前管理web和客户端都很正常啊,到底问题出在那里啊,好心人帮我分析分析
另外,用管理员用户进去,可以打开不能登陆用户的表等数据,就是其他用户登录不上啊
SQL> archive log list
Database log mode
No Archive Mode
Automatic archival
Disabled
Archive destination
USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 96918
Current log sequence 96920
回复

使用道具 举报

千问 | 2014-9-12 22:37:43 | 显示全部楼层
还在做instance recover?看看alert log
shutdown abort慎用!
现在出问题了,你就等得及了?呵呵
回复

使用道具 举报

千问 | 2014-9-12 22:37:43 | 显示全部楼层
登录时候输入用户名、密码后,一直没反应,也不报错,持续几个小时也是这样,急死我了,好心人帮帮我!!!!!
回复

使用道具 举报

千问 | 2014-9-12 22:37:43 | 显示全部楼层
确认是在做instance recovery么?
回复

使用道具 举报

千问 | 2014-9-12 22:37:43 | 显示全部楼层
把alert.log的最后30行发上来
回复

使用道具 举报

千问 | 2014-9-12 22:37:43 | 显示全部楼层
别笑我啊,alert.log半天我都没有找到,按照文件名全盘搜索也没找到,不知道怎么看啊
回复

使用道具 举报

千问 | 2014-9-12 22:37:43 | 显示全部楼层
应该在$ORACLE_BASE/admin/orcl/bddump/alert_orcl.log下
回复

使用道具 举报

千问 | 2014-9-12 22:37:43 | 显示全部楼层
哦,日志在bdump下的alert_myorcl1.log
tail -150 alert_myorcl1.log
sga_target
= 1207959552
control_files
= /u01/app/oracle/oradata/myorcl1/control01.ctl, /u01/app/oracle/oradata/myorcl1/control02.ctl, /u01/app/oracle/oradata/myorcl1/control03.ctl
db_block_size
= 8192
__db_cache_size
= 536870912
compatible
= 10.1.0.2.0
db_file_multiblock_read_count= 16
db_recovery_file_dest= /u01/app/oracle/flash_recovery_area
db_recovery_file_dest_size= 2147483648
undo_management
= AUTO
undo_tablespace
= UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain
=
dispatchers
= (PROTOCOL=TCP) (SERVICE=myorcl1XDB)
job_queue_processes= 10
background_dump_dest = /u01/app/oracle/admin/myorcl1/bdump
user_dump_dest = /u01/app/oracle/admin/myorcl1/udump
core_dump_dest = /u01/app/oracle/admin/myorcl1/cdump
db_name
= myorcl1
open_cursors
= 300
pga_aggregate_target = 399507456
PMON started with pid=2, OS id=6101
MMAN started with pid=3, OS id=6103
DBW0 started with pid=4, OS id=6105
LGWR started with pid=5, OS id=6107
CKPT started with pid=6, OS id=6109
SMON started with pid=7, OS id=6111
RECO started with pid=8, OS id=6113
Tue Feb 24 18:08:20 2009
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
CJQ0 started with pid=9, OS id=6115
Tue Feb 24 18:08:20 2009
starting up 1 shared server(s) ...
Tue Feb 24 18:08:20 2009
ALTER DATABASE MOUNT
Tue Feb 24 18:08:20 2009
Controlfile identified with block size 16384
Tue Feb 24 18:08:25 2009
Setting recovery target incarnation to 1
Tue Feb 24 18:08:25 2009
Successful mount of redo thread 1, with mount id 1860621524
Tue Feb 24 18:08:25 2009
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Tue Feb 24 18:08:25 2009
ALTER DATABASE OPEN
Tue Feb 24 18:08:25 2009
Beginning crash recovery of 1 threads
Tue Feb 24 18:08:26 2009
Started redo scan
Tue Feb 24 18:08:26 2009
Completed redo scan
187 redo blocks read, 13 data blocks need recovery
Tue Feb 24 18:08:26 2009
Started redo application at
Thread 1: logseq 96919, block 6342, scn 0.0
Tue Feb 24 18:08:26 2009
Recovery of Online Redo Log: Thread 1 Group 1 Seq 96919 Reading mem 0
Mem# 0 errs 0: /u01/app/oracle/oradata/myorcl1/redo01.log
Tue Feb 24 18:08:26 2009
Completed redo application
Tue Feb 24 18:08:26 2009
Completed crash recovery at
Thread 1: logseq 96919, block 6529, scn 0.1131131432
13 data blocks read, 13 data blocks written, 187 redo blocks read
Tue Feb 24 18:08:27 2009
Thread 1 advanced to log sequence 96920
Maximum redo generation record size = 120832 bytes
Maximum redo generation change vector size = 116476 bytes
Private_strands 6 at log switch
Thread 1 opened at log sequence 96920
Current log# 2 seq# 96920 mem# 0: /u01/app/oracle/oradata/myorcl1/redo02.log
Successful open of redo thread 1
Tue Feb 24 18:08:28 2009
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Tue Feb 24 18:08:28 2009
SMON: enabling cache recovery
Tue Feb 24 18:08:28 2009
Successfully onlined Undo Tablespace 1.
Tue Feb 24 18:08:28 2009
SMON: enabling tx recovery
Tue Feb 24 18:08:28 2009
Database Characterset is ZHS16GBK
Tue Feb 24 18:08:28 2009
Starting background process QMNC
QMNC started with pid=20, OS id=6216
Tue Feb 24 18:08:28 2009
replication_dependency_tracking turned off (no async multimaster replication found)
Tue Feb 24 18:08:28 2009
Starting background process MMON
Starting background process MMNL
MMON started with pid=21, OS id=6218
MMNL started with pid=22, OS id=6220
Tue Feb 24 18:08:28 2009
Completed: ALTER DATABASE OPEN
Tue Feb 24 18:08:32 2009
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Tue Feb 24 18:29:47 2009
Archive Log Start
ARCHIVE LOG START has been deprecated - see ALTER DATABASE ARCHIVELOG
Tue Feb 24 18:43:38 2009
Starting background process EMN0
EMN0 started with pid=24, OS id=6657
Tue Feb 24 18:43:38 2009
Shutting down instance: further logons disabled
Tue Feb 24 18:43:39 2009
Stopping background process QMNC
Tue Feb 24 18:43:39 2009
Stopping background process CJQ0
Tue Feb 24 18:43:41 2009
Stopping background process MMNL
Tue Feb 24 18:43:42 2009
Stopping background process MMON
Tue Feb 24 18:43:43 2009
Shutting down instance (immediate)
License high water mark = 19
Tue Feb 24 18:43:43 2009
Stopping Job queue slave processes
Tue Feb 24 18:43:43 2009
Job queue slave processes stopped
Tue Feb 24 18:48:50 2009
Active call for process 6224 user 'oracle' program 'oraclemyorcl1@glgk-sv'
Active call for process 6397 user 'oracle' program 'oraclemyorcl1@glgk-sv'
Active call for process 6399 user 'oracle' program 'oraclemyorcl1@glgk-sv'
Active call for process 6422 user 'oracle' program 'oraclemyorcl1@glgk-sv'
Active call for process 6496 user 'oracle' program 'oraclemyorcl1@glgk-sv'
Active call for process 6569 user 'oracle' program 'oracle@glgk-sv (TNS V1-V3)'
Active call for process 6230 user 'oracle' program 'oraclemyorcl1@glgk-sv'
Active call for process 6232 user 'oracle' program 'oraclemyorcl1@glgk-sv'
Active call for process 6234 user 'oracle' program 'oraclemyorcl1@glgk-sv'
Active call for process 6236 user 'oracle' program 'oraclemyorcl1@glgk-sv'
Active call for process 6238 user 'oracle' program 'oraclemyorcl1@glgk-sv'
Active call for process 6240 user 'oracle' program 'oraclemyorcl1@glgk-sv'
Active call for process 6243 user 'oracle' program 'oraclemyorcl1@glgk-sv'
Active call for process 6247 user 'oracle' program 'oraclemyorcl1@glgk-sv'
Active call for process 6253 user 'oracle' program 'oraclemyorcl1@glgk-sv'
Active call for process 6287 user 'oracle' program 'oraclemyorcl1@glgk-sv'
Active call for process 6292 user 'oracle' program 'oraclemyorcl1@glgk-sv'
SHUTDOWN: waiting for active calls to complete.
Tue Feb 24 19:04:12 2009
KTSMG_UPDATE_MQL(): MMNL absent for 1287 secs; Foregrounds taking over
Tue Feb 24 19:45:09 2009
SHUTDOWN: Active sessions prevent database close operation
Tue Feb 24 22:10:30 2009
Adjusting the default value of parameter parallel_max_servers
from 160 to 135 due to the value of parameter processes (150)
Tue Feb 24 22:10:30 2009
Starting ORACLE instance (normal)
回复

使用道具 举报

千问 | 2014-9-12 22:37:43 | 显示全部楼层
。。。你的数据库还没有打开呢....
问题是为啥 instance都无法启动...
回复

使用道具 举报

千问 | 2014-9-12 22:37:43 | 显示全部楼层
你确定你贴全了?如果确定,建议你现在重新启动机器吧,连instance都无法打开。估计内存中有东西没有释放...
还有你说你shutdown abort关闭了数据库,但是log中没有看到abort成功的纪录
[ 本帖最后由 zergduan 于 2009-2-24 23:45 编辑 ]
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

主题

0

回帖

4882万

积分

论坛元老

Rank: 8Rank: 8

积分
48824836
热门排行