My understanding, and a quick google confirmed what I thought, is that they are essentially the same thing. A FULL backup is a backup of ALL data up until that point in time. My understanding is that an Oracle Archive Log is similar to a SQL Server Log Backup in that it has the data that has changed since the last backup.
The link I found - https://stackoverflow.com/questions/62713005/why-we-have-to-backup-archive-log-after-backup-full-db#:~:text=All%20archive%20logs%20backup%20is%20not%20needed.%20and,log%20backup%20once%20full%20DB%20backup%20is%20taken%29
which states "Archived redo logs are used in case you lost your data due to any situation: DB crashed, data corruption, or any. In such a situation archive logs (from the last backup taken to a time when DB is corrupted) are used." The example they give is that in the event of corruption, you can restore from the FULL and then restore the LOG.
So, to do a restore, in both SQL and Oracle, if you have a FULL backup only, you restore from that BUT it will only have data up until the time the backup was taken. So if you do the full backup at midnight daily and you want data from today at noon, you would need to wait until the next full backup at midnight before you could see that data. However, if you do log backups or differential backups, you can get to a better point in time prior to the latest log backup.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.