.trc文件的错误内容*** MODULE NAME:(DBMS_SCHEDULER) 2008-07-17 22:00:17.321*** SERVICE NAME:(SYS$USERS) 2008-07-17 22:00:17.321*** SESSION ID:(495.2004) 2008-07-17 22:00:17.321ORA-01723: zero-length columns are not allowed*** 2008-07-17 22:00:17.328GATHER_STATS_JOB: GATHER_TABLE_STATS('"hcl"','"F_LN_LNP_COOP_xx"','""', ...)ORA-01723: zero-length columns are not allowed*** 2008-07-17 22:00:18.677GATHER_STATS_JOB: GATHER_TABLE_STATS('"hcl"','"F_LN_LNP_MNG_xx"','""', ...)ORA

rt

现在有个库需要从ZHS16GB231280到ZHS16GBK现考虑步骤如下：导出数据export NLS_LANG=american_america.ZHS16GB231280exp system/xxxxx导入数据export NLS_LANG=american_america.ZHS16GBKimp system/xxxx这2个字符集的设置是否正确，导入的时候设置肯定是对的，exp的时候，是设置成gb2312还是gbk，或者是都可以？[ 本帖最后由 hcl 于 2008-5-28 17:24 编辑 ]

SQL> select switchover_status,guard_status,database_role from v$database;SWITCHOVER_STATUSGUARD_S DATABASE_ROLE-------------------- ------- ----------------NOT ALLOWEDNONEPRIMARYSQL> alter database commit to switchover to physical standby;alter database commit to switchover to physical standby*ERROR at line 1:ORA-16416: Switchover target is not synchronized with the primary怎样才能把switchover_status的状态为to standby;

客户说在informix中一个表的extent过多就会出现insert失败。在oracle中extent过多有什么影响和限制吗？参考：http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/limits002.htm#i287915Database extents Maximum per dictionary managed tablespace 4 GB * physical block size (with K/M modifier); 4 GB (without K/M modifier)Maximum per locally managed (uniform) tablespace 2 GB * physical block size (with K/M modifier); 2 GB (without K/M modifier)MAXEXTENTS Default value

Oracle Server - Enterprise Edition - Version: 10.2.0.3HP-UX PA-RISC (64-bit)alert_hcl.logTue Apr 22 08:55:16 2008Errors in file /home/db/oracle/admin/hcl/udump/hcl_ora_10557.trc:ORA-03135: connection lost contacthcl_ora_10557.trc里错误是："File '/dev/async' not present : errno=2"我查了下metalink，如下：Applies to:Oracle Server - Enterprise Edition - Version: 10.2.0.2 to 10.2.0.3HP-UX PA-RISC (64-bit)SymptomsAfter upgrading a database to 10.2.0.2 or 10.2.0.

在２个节点上的clustered状态都是yes,并且vg access是read/write我先用sqlplus / as sysdba启动node1上的instance,可以成功；然后用sqlplus / as sysdba启动node2上的instance,可以成功，但，启动后我发现node1上的实例自动关闭了。还有一个问题，上面的vgdisplay中clustered=yes,shared=no有什么影响吗，分别是什么意思？[PHP]node1:[root@node1 ~]# vgdisplay datavg--- Volume group ---VG NamedatavgSystem IDFormatlvm2Metadata Areas

tablespace test有a,b两个表truncate table a;insert into b xx;commit;然后，我发现a表truncate错了，我也不想丢失b表之后插入的数据，如何用rman快速恢复a表？btw:有truncate前的rman全库备份，数据库归档状态。[ 本帖最后由 hcl 于 2008-3-31 11:50 编辑 ]