Hi,
I have done the same mistake in the past but on one database devices not the log devices.
This is what I did to reduce the space which was a bit tricky.
In your instance I think you should be able to stop the application, dump transaction saptools dump transaction SID using config = 'SIDLOG' if you have dump configured.
For log you could use my procedure , still with application offline and DB only running in single user mode. Also make full backups beforehand as always is good practice.
Instead of alter database <database> off you wold change syntax from this:
alter database databasename off database_data_File-'60000M'
go
to this:
alter database saptools log off logsaptools_1="60000M"
go
I think you will first have to add a secondary smaller log device i.e. logsaptools_2 and once you have reclaimed used space from logsaptools_1 you should be able to drop and recreate it with the correct small size. I would also suggest you add auto extending on the tablespaces etc via dbacockpit. The off and log off is a long running process too me several nights after hours to correct.
As for the log off procedure just confirm but it should hold true, but I am speaking under possible correction.
Kind Regards,
Johan
If you are unsure rather confirm with SAP AG.