加载大数据文件时出现 ORA-00054
我在加载大型数据文件(~ 10 GB)时收到 ORA-00054 当在上一个文件之后加载新文件时,会发生错误。 我有什么想法可以解决这个问题吗?
I get ORA-00054 while loading large data files(~ 10 gb)
The error occurs when this a new file is loaded after a previous file.
Any ideas how I can solve this?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(4)
一种可能的情况。
这是直接路径加载吗?如果是这样,请检查 v$locked_object 视图,看看在加载过程中是否被某人锁定。
来自 Oracle 文档,网址为 http://download.oracle。 com/docs/cd/B10500_01/server.920/a96524/c21dlins.htm
One possible scenario.
Is this a direct path load ? If so, please check the v$locked_object view and see if is being locked by someone during your load.
From the Oracle Documentation at http://download.oracle.com/docs/cd/B10500_01/server.920/a96524/c21dlins.htm
也许这与表空间数据文件大小、表大小有关,因为 ORA-00054 通常在运行 ALTER 语句时出现。
我不会假装就在这里。
Maybe this is linked to tablespace datafile sizes, table size, because ORA-00054 usually appears when an ALTER statement is run.
I do not pretend to be right here.
检查这些观点。
DBA_BLOCKERS – 显示持有正在等待的锁的非等待会话
DBA_DDL_LOCKS – 显示持有或正在请求的所有 DDL 锁
DBA_DML_LOCKS - 显示持有或正在请求的所有 DML 锁
DBA_LOCK_INTERNAL – 每个锁或闩锁显示 1 行使用持有锁的用户名持有或正在请求
DBA_LOCKS - 显示所有锁或闩锁已持有或正在请求
DBA_WAITERS - 显示所有正在等待但未持有等待锁的会话
http://www.dba-oracle.com/t_ora_00054_locks.htm
Check those views.
DBA_BLOCKERS – Shows non-waiting sessions holding locks being waited-on
DBA_DDL_LOCKS – Shows all DDL locks held or being requested
DBA_DML_LOCKS - Shows all DML locks held or being requested
DBA_LOCK_INTERNAL – Displays 1 row for every lock or latch held or being requested with the username of who is holding the lock
DBA_LOCKS - Shows all locks or latches held or being requested
DBA_WAITERS - Shows all sessions waiting on, but not holding waited for locks
http://www.dba-oracle.com/t_ora_00054_locks.htm
您的表似乎已锁定:ORA-00054
这可能是因为 Oracle 驱动程序处理 BLOB 类型的方式(驱动程序锁定记录、打开流来写入二进制数据,并且需要“一些帮助”来释放记录)。
我会尝试下一步:
Your table seems to be locked: ORA-00054
It can be because of the way that Oracle driver handles the BLOB types (the driver locks the record, opens an stream to write the binary data, and needs "some help" to release the record).
I would try the next secuence: