"Thread 1 cannot allocate new log"I know that this usually means the redo logs are too small or too few, but I'm wondering whether there is a connection with the TEMP tablespace, which I noticed has filled up to 99.98% full. This is a problem I was already aware of and am going to extend asap, but I wondered whether this will solve the redo log problem, or whether the two issues are entirely separate.
The issues are separate. The amount of space used in the TEMP tablespace does not have any bearing on redo log performance, and vice versa.
Dig Deeper on Oracle database design and architecture
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.