Concurrent Execution of DROP TABLE and SHRINK TABLE: Safety and Archive Log Impact

When managing database tables, I have two related questions. First, is it safe to execute DROP TABLE and SHRINK TABLE commands at the same time if they are being applied to different tables? Are there any potential conflicts or issues that might arise from running these operations concurrently?

Second, while I understand that running SHRINK TABLE on multiple tables can generate a significant amount of archive logs, I’m curious whether the DROP TABLE command also results in a substantial increase in archive log output. Could you clarify the impact of DROP TABLE on archive log generation?

Version : 10.2.0.5.0