Many database connections don't like more than a single active statement handle that hasn't been completely fetched ("cursor"). I know that SQLite dislikes this.

My usual approach is to either convert the two parallel SQL statements into a single SQL statement, likely with a JOIN, or to use ->fetchall_arrayref to first read all of the rows of the first statement and then process the second statement. My machines usually have enough memory for the second approach.